-
-
Notifications
You must be signed in to change notification settings - Fork 182
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
MonacoEditorReactComp not fires onTextChanged callback if you change code resource #697
Comments
HI @lobotomoe thank you for reporting this and providing a re-producible example. We will investigate... |
@lobotomoe the file changes are not provoking |
@kaisalmen Thanks for the answer! I'm not sure if it's worth bothering so much purely because of my case, but I don't mind if there's a flag 😀 Currently I'll try your approach with ref and manual trigger |
@lobotomoe we want to transform the ClassComponent to a FunctionalComponent and when we will do it think about this use case. |
@lobotomoe #739 is merged, but not yet released. It will take some time because it will be a major version and there are other things that should be included as well. I will take a look if we can build a unit test for this problem now... |
@lobotomoe can you try the latest preview build: https://www.npmjs.com/package/@typefox/monaco-editor-react/v/6.0.0-next.5 ? |
I try to use
@typefox/monaco-editor-react
with multiple files, but only for first file callbackonTextChanged
fired.Repro repo: https://github.com/lobotomoe/monaco-on-text-changed-issue
Steps for repro:
Try to type something and you will see in console that
onTextChanged
fired. Switch to second file. Try to type — nothing happens. Switch back to first file, try to type — callback fires.See video demo:
demo.mp4
The text was updated successfully, but these errors were encountered: