fix(files): workspace implementation#7418
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #7418 +/- ##
==========================================
- Coverage 52.63% 52.61% -0.02%
==========================================
Files 494 494
Lines 42296 42284 -12
Branches 1088 1088
==========================================
- Hits 22261 22248 -13
- Misses 19928 19929 +1
Partials 107 107 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
max-nextcloud
left a comment
There was a problem hiding this comment.
Two minor nitpicks - other than that looks great. Thanks for taking care of this so quickly!
❤️
Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
|
Done @max-nextcloud 👍 |
|
/backport to stable31 |
|
Testing out if this helps with rich workspace tests failing in stable31 lately. |
|
@max-nextcloud seems like when you load an existing workspace, clicking the content doesn't trigger the editor mode anymore 🤔 |
|
@skjnldsv I'll take a look. Thanks for the heads up. |
|
Ah, nice catch! |
|
I suspect this broke due to a later change in server. Otherwise i don't see how the cypress tests would have passed as they test editing the workspace. update: most cypress tests pass locally for me as they create the workspace and then test it. - and that works fine. 💭 thinking out loud |

Might require nextcloud/server#53872
Master have received a few fixes, the current workspace implementation wasn't optimal, so I fixed it.
newWorkspaceCreatedfiles:node:updatedto dispatch the fact that the current folder have changed (and update the workspace attributes accordingly)