Fix double readme files getting created on case-insensitive storages #4104
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.
Fix #3348
Apparently this got missing from #834 when the rebase was done.
See https://github.com/nextcloud/text/compare/1e600fb26111f0c850f134cf17aad96b1c8c59d3..7d6569cdf4c01e3467fe4b066a5f80bb56c48d9e
But actually @max-nextcloud and me tested a bit and this only seems to fix when creating new readme files from the workspace. The rootcase would probably need to be fixed somewhere in getFileInfo in View.php in server but we don't know much about that so adding this change here seems like a quick win.