-
Notifications
You must be signed in to change notification settings - Fork 94
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
fix: Properly emit ready event on conflicts with the editor API #4028
Conversation
2 flaky tests on run #9392 ↗︎
Details:
sync.spec.js • 1 flaky test
share.spec.js • 1 flaky test
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. |
Also fixes this issue on Collectives as there the parent component is the |
/backport to stable26 |
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.
Thanks for tackeling this @juliushaertl. Code looks good to me 👍
9ae3314
to
c5386b2
Compare
Signed-off-by: Julius Härtl <jus@bitgrid.net>
Signed-off-by: Julius Härtl <jus@bitgrid.net>
c5386b2
to
94160a9
Compare
/compile |
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
📝 Summary
Fixes loading the editor integrated through the editor API when a file conflict occurs during the initial loading. In this case the ready event was never emitted on the root component that would pass the state to the notes app.
I'd love to have a more generic way there but haven't found a proper way to avoid emitting on both this and parent, so the second commit cleans up the emit handling in Editor.vue to make sure we always emit on both.
🏁 Checklist
npm run lint
/npm run stylelint
/composer run cs:check
)