fix: prevent annexed files to be edited with WebUI #135
Conversation
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
"IsAnnexedFile" flag was set to true when the annexed content could not be loaded, hence to avoid misunderstanding it's renamed "UnavailableAnnexedContent".
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 for issue #134: Restore what seems to be the previous behaviour, namely preventing annexed files to be edited in the WebUI.
Indeed annexed content detection at :
gogs/internal/route/repo/view.go
Line 235 in 966e925
would inevitably fail since file content has already been replaced by annexed content at :
gogs/internal/route/repo/view.go
Line 149 in 966e925