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
fix: parent directory permissions #128
fix: parent directory permissions #128
Changes from 33 commits
5a9e828
e283b54
5b4a669
0b971ec
c05849e
8843df7
f0f3373
c66ee38
5dcb35d
2454adf
8fdb140
02cc088
e654732
b245f35
5e9eb2f
3d84be3
622e346
b2d22d9
bb9dc02
f7887d2
a9b8c02
a2805d0
23e5e15
21eea9e
9a55a36
2f12765
ccc7ff5
241cedf
acfe93e
847ecb3
75b82b5
387477a
5849477
eb21499
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.
This is not looking right, for two reasons:
We've added a flag to control behavior that was standard until this commit, meaning every single call site for the Create function was the equivalent of OverrideMode: true. Yet, we're not using this flag anywhere apparently, which means it's false 100% of the time and the behavior has been disabled. That implies to me that the old behavior has turned irrelevant after the last couple of changes, so we can just drop the behavior altogether.
This flag doesn't seem to sit well in the API as a whole. It doesn't make sense for this flag to work only on directories, for example.
GIven (1), what's the situation? Can we just delete the behavior altogether?
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.
Agree with both. I was keeping it for future compatibility but when we need it we can just add it back to the API. Deleting unused code is the best code.