Feat/proactive token validation before requests #111
+122
−9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces an optional
shouldRefreshBeforeRequest
callback to the Fresh library. The new callback allows for proactive token validation before making requests, ensuring that tokens are refreshed when necessary, reducing the risk of sending requests with expired tokens.This PR aims to address issue #110
Key Changes
shouldRefreshBeforeRequest
callback to bothFresh
andFreshLink
:onRequest
interceptor.Usage Example
Discussion
The current name,
shouldRefreshBeforeRequest
, could be revised for clarity and alignment with library conventions. Open to feedback on naming and implementation.