fix: deleting rich workspaces readme.md

[luka-nextcloud]

📝 Summary

• Resolves: Loading error after deleting rich workspaces readme.md #4525

🖼️ Screenshots

🏚️ Before	🏡 After
B	A

🚧 TODO

• ...

🏁 Checklist

• Code is properly formatted (npm run lint / npm run stylelint / composer run cs:check)
• Sign-off message is added to all commits
• Tests (unit, integration and/or end-to-end) passing and the changes are covered with tests
• Documentation (README or documentation) has been updated or is not required

[cypress]

3 failed and 1 flaky tests on run #12061 ↗︎

3

137

18

0

1

Details:

fix: deleting rich workspaces readme.md
Project: Text	Commit: 5af1cd1588
Status: Failed	Duration: 04:48 💡
Started: Sep 7, 2023 4:49 PM	Ended: Sep 7, 2023 4:54 PM

  cypress/e2e/attachments.spec.js • 3 failed tests

View Output Video

Test		Artifacts
Test all attachment insertion methods > test if attachment folder is moved with the markdown file		Output Screenshots
Test all attachment insertion methods > test if attachment folder is copied when copying a markdown file		Output Screenshots
Test all attachment insertion methods > [share] check everything behaves correctly on the share target user side		Output Screenshots

  cypress/e2e/files.spec.js • 1 flaky test

View Output Video

Test		Artifacts
Text and server mimetypes > handle markdown with richtext editor		Output Screenshots

_{This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.}

[max-nextcloud]

Code looks good. Cypress test would be nice to avoid regressions in the future.

[luka-nextcloud]

@max-nextcloud @juliushaertl I found that cypress tests for workspace was set to skip here
Should we enable them again?
It seems like there are many errors while enabling them. Please check below screenshot. Should we fix them in this PR?
Test case for above issue already included in case "Hides the workspace when switching to another view". But need small update.

[mejo-]

@luka-nextcloud I agree that we certainly should re-enalble the Cypress tests for rich workspaces. Seems like skipping them was meant as temporary in db7aa50 anyway. Maybe you can take a look at fixing the Cypress tests?

[max-nextcloud]

I think a first step towards this would be running the current master branch locally and checking how rich workspaces work there. Maybe some of the functionality is still missing.

[luka-nextcloud]

@mejo- @max-nextcloud I'd suggest to open a separate ticket for the cypress work, what do you think?

[mejo-]

@luka-nextcloud I'm fine with this. Could you open the issue?

[luka-nextcloud]

Here's a separate ticket: #4829