-
Notifications
You must be signed in to change notification settings - Fork 263
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
Changing the value in store will not update the component & contents #121
Comments
+1 |
I also have this issue |
@OsamaShabrez @zane-c @marcofugaro hey all, I too was having similar issues and threw up react-codemirror2 which doesn't seem to suffer from this. I'm planning to maintain it moving forward. Feel free to open up an issue on the repo should anything seem off and I'll be on it 😎 |
here's the offending commit 339b597 |
Had to downgrade react-codemirror due to a bug. Issues and PRs are open to resolve: - JedWatson/react-codemirror#121 - JedWatson/react-codemirror#106
ugly hack:
and then in the code where you want to update: |
@JedWatson can you take a look at 339b597 and possibly just reverse it as @jaredly pointed out? |
Had to downgrade react-codemirror due to a bug. Issues and PRs are open to resolve: - JedWatson/react-codemirror#121 - JedWatson/react-codemirror#106
Had to downgrade react-codemirror due to a bug. Issues and PRs are open to resolve: - JedWatson/react-codemirror#121 - JedWatson/react-codemirror#106
Had to downgrade react-codemirror due to a bug. Issues and PRs are open to resolve: - JedWatson/react-codemirror#121 - JedWatson/react-codemirror#106
Had to downgrade react-codemirror due to a bug. Issues and PRs are open to resolve: - JedWatson/react-codemirror#121 - JedWatson/react-codemirror#106
I just spent an hour chasing this bug. 🤦🏻♀️ Thanks for the (working) fork, @scniro! |
If CodeMirror value is changed at the backend, directly in the store the component does not reflect the latest changes.
There is no way I have found so far that can force update the component. Any help would be greatly appreciated.
The text was updated successfully, but these errors were encountered: