Allow for custom expiration based on request #65
Merged
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.
This breaks out an
get_expire_seconds
method that simply gets theEXPIRE_AFTER
value from the config. My thinking is that this should allow things like #58 to be solved by the end-user easily though creating a new middleware that overrides theget_expire_seconds
method. For example, if they want per-user settings they'd have to create a User Profile model to store the timeout, then they could just do something like:(* example not guaranteed to work)