New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add logs to msal-browser #3004
Add logs to msal-browser #3004
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One non-blocking comment. Can be done incrementally if that makes more sense.
change/@azure-msal-browser-3e900bbd-5fb6-4800-9cf5-beeaefbc5e47.json
Outdated
Show resolved
Hide resolved
@@ -288,6 +295,7 @@ export class BrowserCacheManager extends CacheManager { | |||
* @param appMetadataKey | |||
*/ | |||
getAppMetadata(appMetadataKey: string): AppMetadataEntity | null { | |||
this.logger.verbose("BrowserCacheManager.getAppMetadata called"); | |||
const value = this.getItem(appMetadataKey); | |||
if (!value) { | |||
return null; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In each of the getters should we also log whether or not we successfully found something in the cache?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense. I added cache hit logs, and it makes the logs a lot longer. If we discover it creates too much noise, I'm happy to remove them later.
…7.json Co-authored-by: Thomas Norling <thomas.l.norling@gmail.com>
This PR: