Fix for either over- or under-specific file permissions #1279
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.
As reported a few times by @jdbocarsly and @PeterKraus, file permissions are currently too all-or-nothing; either all users who know the file ID should be able to access it (typically only possible if they have access to the item that the file is attached to), or they have to have full access to the file as an uploader. The former approach is problematic, as a user may lose permissions but still be able to access the file.
This PR alters that by tying file permissions to the item permissions more directly. This is a semi-temporary fix until full granular object permissions are implemented, but I imagine this will be the default after that refactor anyway.