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.
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
Improve Visible History to support more general time queries #4123
Improve Visible History to support more general time queries #4123
Changes from 4 commits
e6a0eba
36058ec
adce254
9c01f7f
6f4517e
648dcf9
dc39ea7
34608e0
c5b04d9
00629fc
2d82812
acd1a0e
5ddf00a
bf65bf6
6bc0ba7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
to clarify, when can it happen that one is off but the other is enabled?
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.
How the visible history is stored is not fully normalised: there is a slight duplication:
{from: Relative(0), to: Relative(0)}
(that's whatVisibleHistory::OFF
is) disable the feature for all practical purposes.I've introduced that "enabled" bool to allow the user to disable the feature without losing their configured boundaries (ie. that checkbox next to the
Visible History
label). Overall, better UX I believe, but the cost is this check.BTW, the test against
VisibleHistory::OFF
could actually be dropped and the result would be the same. So it can be seen as an optimisation to avoid a range query when we know none is needed :)