-
Notifications
You must be signed in to change notification settings - Fork 184
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
reva/frontend: Add capabilities to indicate attributes that are read-only #6047
reva/frontend: Add capabilities to indicate attributes that are read-only #6047
Conversation
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
Please add some text to readme.md to reflect the changes on the envvar side. |
4e9c413
to
f5b2d98
Compare
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.
LGTM from a docs pov, but needs a dev reviewer approval too
@mmattel this has changed in the reva implementation. We will have only one config value and a list of strings. |
Co-authored-by: Martin <github@diemattels.at>
de6c4bc
to
e52a507
Compare
e52a507
to
9a2ecf4
Compare
9a2ecf4
to
1938495
Compare
@Excds Can we make the adjustments and merge this today to unblock the frontend team? |
AFAICT there is no reva update inside this PR, this will be needed to make the changes work. |
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.
One more question
Co-authored-by: Martin <github@diemattels.at>
Kudos, SonarCloud Quality Gate passed! |
…_indicating_read-only_attributes reva/frontend: Add capabilities to indicate attributes that are read-only
This adds capabilities indicating if certain attributes are read-only.
Companion PR: cs3org/reva#3789