enh: add read-only property to view columns (backend only) - #1916
Closed
blizzz wants to merge 1 commit into
Closed
Conversation
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
1 task
Contributor
|
Mate, I've took your PR as an inspiration point and implemented whole functionality in #1958. Please check when you have time 馃檹 |
Member
Author
Contributor
|
I believe it's safe to close this, since #1958 is done |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
contributes to #1154
Currently work in progress.
The approach is here to to still continue with the save operation and only leave out a provided column value if it is set to read-only instead to throw an error for the whole request.