We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Lexical version: 0.17.1
From #6625 (comment)
npm run start
npm run test-e2e-chromium
Fails because the websocket doesn't stay connected. I suspect this is a React strict mode related issue. CI doesn't test dev mode.
Websocket stays connected
I suspect that it would be pretty hard to work on collab right now with dev mode broken?
The text was updated successfully, but these errors were encountered:
Could be related to #6271
Sorry, something went wrong.
Also related #6619
Fix facebook#6640 by reverting to disconnect timing from before faceb…
f43f344
…ook#6619 for sync provider.connect
Successfully merging a pull request may close this issue.
Lexical version: 0.17.1
Steps To Reproduce
From #6625 (comment)
npm run start
npm run test-e2e-chromium
(from another terminal)The current behavior
Fails because the websocket doesn't stay connected. I suspect this is a React strict mode related issue. CI doesn't test dev mode.
The expected behavior
Websocket stays connected
Impact of fix
I suspect that it would be pretty hard to work on collab right now with dev mode broken?
The text was updated successfully, but these errors were encountered: