-
Notifications
You must be signed in to change notification settings - Fork 274
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
BLO-838 chore: use endpoint to determine token expiry #1842
Conversation
await jwtFetcher(`${ARGENT_API_BASE_URL}/account`) | ||
return false | ||
} catch (error) { | ||
IS_DEV && console.warn(coerceErrorToString(error)) |
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.
I've seen this pattern elsewhere but why collect logs only in dev mode ?
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.
The logs can be informative if the service might return unexpected errors as it can here. This has already been useful for debugging with be. Dev only so they don't end up leaking unnecessarily into a prod build.
21f7f4a
to
874ca5b
Compare
Kudos, SonarCloud Quality Gate passed! |
Issue / feature description
Can use endpoint to check token expiry (excluding for removal)
Changes
Checklist