Add posibility to set up cookies max-age in runtime #81
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Looks great. Thanks for contributing! 👍 |
|
I'll get a new release out later today with these changes. Thanks! |
|
Sorry, this slipped my mind the other day. It is released as 3.3.0 now. Cheers. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Now it is not flexible to have only two options for cookie max-age time:
It force developer to handle expirations for refresh token in cookies explicit
(if i get correctly expired refresh token handled by the same expired_token_loader decorator as access tokens, and there is not any special ad-hoc decorator for it ).
This change provide option for developer to define max-age in call time