Bläddra i källkod

refactor: improve comments for access token parsers for clarity

Shun Miyazawa 7 månader sedan
förälder
incheckning
d8cec4beea

+ 1 - 0
apps/app/src/server/middlewares/access-token-parser/access-token.ts

@@ -13,6 +13,7 @@ const logger = loggerFactory('growi:middleware:access-token-parser:access-token'
 export const parserForAccessToken = (scopes: Scope[]) => {
   return async(req: AccessTokenParserReq, res: Response): Promise<void> => {
     // Extract token from Authorization header first
+    // It is more efficient to call it only once in "AccessTokenParser," which is the caller of the method
     const bearerToken = extractBearerToken(req.headers.authorization);
 
     const accessToken = bearerToken ?? req.query.access_token ?? req.body.access_token;

+ 1 - 0
apps/app/src/server/middlewares/access-token-parser/api-token.ts

@@ -14,6 +14,7 @@ const logger = loggerFactory('growi:middleware:access-token-parser:api-token');
 
 export const parserForApiToken = async(req: AccessTokenParserReq, res: Response): Promise<void> => {
   // Extract token from Authorization header first
+  // It is more efficient to call it only once in "AccessTokenParser," which is the caller of the method
   const bearerToken = extractBearerToken(req.headers.authorization);
 
   // Try all possible token sources in order of priority