value prop changes are not reflected
See original GitHub issueReact-Quill version: 2.0.0-beta.1
It seems value prop changes can’t change internal quill editor contents. I expect this codesandbox quill contents to be changed every 1 second, but it doesn’t.
I suspect shouldComponentUpdate
blocks componentDidUpdate
call taking charge of reflecting value changes.
How about adding value
to cleanProps
?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:10 (2 by maintainers)
Top Results From Across the Web
React: why child component doesn't update when prop changes
It won't be reflected in Child component until we change its key. We have to save that on child's state and then change...
Read more >Why React Child Components Don't Update on Prop Changes
In React, it's a common problem to have child components that don't re-render when you expect them to. In particular, a common problems...
Read more >Why useEffect is Not Updating When props Change
If the array argument is empty, useEffect will not check any variables for updates, and it will run once and only once. This...
Read more >You Might Not Need an Effect - React Docs
How to remove unnecessary Effects · Updating state based on props or state · Caching expensive calculations · Resetting all state when a...
Read more >DOM not updating when I value of prop changes - Vue Forum
In the parent I am passing 3 variables as props to the child. In the Child I am using the watch() to look...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The bug still appearing in 2.0.0-beta.4 if I update the value and pass that change to the Quill component via value, that change is not reflected.
@pmaddaloni-shujinko @avinashk2946 My codesandbox’s bug behaviour is not reproducible on 2.0.0-beta.2. Your phenomenon may be a separate issue, may have different conditions to reproduce. How about opening a new issue with a reproducible codesandbox?