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
users/config: Improve modTimeWindowS explanation #584
Merged
Merged
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
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
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 know the context of this addition, but I don't think "must be set before adding files to the folder to take effect" increases understanding much here... Any config change only affects what happens after it is made, obviously, but this somehow implies it won't work if set on an existing folder.
Perhaps something in the first sentence about the comparison being used to decide whether a file has changed and needs to be rehashed? Then it might be more clear that changing this option doesn't un-rehash and un-change the file...
Or perhaps this doesn't belong here at all but is an aspect of recv-only folders ("once a local change has been detected in will not become un-detected even if relevant config options change").
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.
Yeah, I know that the sentence is vague. I could not come up with anything better.
What do you think about something like this?
Must be set before adding files to the folder in order to take effect on those files.
Otherwise I will try to think about how to rewrite the sentences to explain the point better.
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 don't particularly like that either, because it makes it sound like the value is somehow locked in per file once we've seen it the first time... while in reality it simply applies each and every time we look at a file and consider the modification timestamp.
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 reworded the explanation a little bit, and also removed the controversial line. I agree that it will be better to explain this behaviour with regards to RO folders in general rather than having separate explanations under each setting.