chore: smart sessions timeframe policy #7
Conversation
This file contains 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
VGabriel45
changed the title
…ore/smart_sessions_timeframe_policy
size-limit report 📦
|
|
I will merge this after rhinestone attest timerange policy across chains |
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.
PR-Codex overview
This PR focuses on updating the session management policies in the
smartSessionsValidatormodule, including adjustments to session validity timings and the introduction of new parameters for action policies.Detailed summary
CHANGELOG.mdwith version 0.0.31 and 0.0.30 changes.sessionValidUntilandsessionValidAfterto useDate.now()for accurate timing.usageLimitandvalueLimitin policy tests.getPermissionActionto include time frame policy data for user operations.