-
-
Notifications
You must be signed in to change notification settings - Fork 987
Only touch sessions in the store when rolling sessions are enabled #531
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
Open
dtymon
wants to merge
8
commits into
expressjs:master
Choose a base branch
from
dtymon:feature/only-touch-rolling-sessions
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
cc345a7
Only touch sessions in the store when rolling sessions are enabled
64ba3e5
Fix tests broken with rolling session change to touch()
b6fb975
Add test to get coverage back to 100%
e313529
Add tests to check touch() suppression when rolling is turned off
abc7b0a
Add option alwaysTouchUnmodified to force unmodified sessions to alwa…
25021df
Fix logic error in documentation of new option
8543451
Revert changes made to tests now that existing behaviour is the default
8d0180b
Move new touching logic into shouldTouch() where it belongs
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
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 forget looking through the comments: is there an intention to make
alwaysTouchUnmodifed
the default behavior in the next major? I ask because all default options that are Booleans should befalse
such thatundefined
andnull
are stand in values. The only options that default totrue
are deprecated options, but this doesn't have a deprecation warning on it.