-
-
Notifications
You must be signed in to change notification settings - Fork 173
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
Update onTextChanged in MonacoEditorReactComp #684
Conversation
Thanks, I'll convert this to a draft until #682 merges and I rebase this |
28e6dc9
to
9b7615a
Compare
@kaisalmen thanks, I've rebased and marked as ready for review |
Those |
@CGNonofr thank you. I guessed that I have to debug it, but there was a small chance you had an idea. Updating to the newest version did not change the behaviour, btw |
Is this a jest test or something? did you override the fetch behavior? |
It is vitest in headless browser mode using chrome via webdriver.io |
Ok, I'm not familiar at all with it, I won't be able to help any further, sorry |
It looks like |
@vrama628 that is exactly the issue. I didn't see that yesterday. I will merge this now and post a fix on main. |
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.
LGTM. Test will be fixed on main
Build pipeline is green again: https://github.com/TypeFox/monaco-languageclient/actions/runs/9702661785 |
Fixes #683
Updates
MonacoEditorReactComp
to correctly handle changes to theonTextChanged
prop.Note: since there isn't a test suite for the React component on
main
, this branch includes changes from both this PR and #681 . See here for a diff of just the changes relevant to this PR.The first commit adds a test case that reproduces the issue, and the second commit fixes it. When I run the test after the fix, Vite seems to get stuck and infinitely hang; I wasn't able to figure out why. I'm open to suggestions on how to fix the test case to run properly in
vitest
, or I can just remove the test case altogether.