Enhancement: add a read-only option to view columns - #1958
Conversation
00fec50 to
2696c27
Compare
|
1000 thanks Would it not be possible that in edition mode those columns do appear but they are greyed out and cannot be entered in. By removing them from edition here you might not know what you are editing. |
433c9d5 to
e035173
Compare
|
@Aveyron-RetD I've updated PR with your suggestion. This approach requires much more changes 😁 . You can observe behavior on the video |
|
\o/ thanks for all your contributions. Hope they all get merged soon. |
e035173 to
f80d3b4
Compare
blizzz
left a comment
There was a problem hiding this comment.
Looks good from backend side, no blockers, 👍
@JuliaKirschenheuter @enjeck can we have a look on the frontend bits, too?
AIlkiv
left a comment
There was a problem hiding this comment.
Thank you for the PR. I have a few minor comments.
3980bb6 to
1cbd076
Compare
d90df48 to
a7420c5
Compare
bcc2aee to
203c23d
Compare
marcoambrosini
left a comment
There was a problem hiding this comment.
Very nice @Koc
The only comment I have for now is I would separate the string into "Read only" in the actions menu
203c23d to
7a121ce
Compare
7a121ce to
682c76f
Compare
|
@marcoambrosini I've updated text string
Cypress test are failing after one of the last rebases and I have no idea why. Can anybody help me with that, please? @enjeck @blizzz |
Signed-off-by: Kostiantyn Miakshyn <molodchick@gmail.com>
…stments) Signed-off-by: Kostiantyn Miakshyn <molodchick@gmail.com>
682c76f to
426b46b
Compare
Signed-off-by: Enjeck C. <patrathewhiz@gmail.com>
I fixed a few, but commented out the readonly attribute check since I can't figure out why it's failing. Even though tests fails, manual checks show they work. I'm fine with merging as-is right now. Stylelint fixed at #2050 |

Closes #1154 and replaces #1916. This PR contains complete implementation for the both BE and FE sides.
🔍 Preview
nextcloud-readonly-tables-2025-07-31_00.39.34.mp4
🚧 Todo: