No longer debounce componentWillReceiveProps #106#107
No longer debounce componentWillReceiveProps #106#107ovidiuch wants to merge 1 commit intoJedWatson:masterfrom ovidiuch:106-fix-update
Conversation
|
Hi @skidding, just wanted to know if you are plan to check this in soon, since IMHO it's not a good idea to debounce a lifecycle event. |
|
@alexandro81 it's not up to me since I don't have write nor publish rights on this project. See this thread for now. |
|
Got it, thanks! |
|
@JedWatson is there any blocker for this? It would be nice to have the fixed checked-in, unless you think there's something wrong in the PR? |
|
Bump |
|
Double Bump! |
|
//cc @JedWatson |
|
@JedWatson If this gets merged, can it be part of a minor release? All our team needed recently was fixing the 15.5 deprecation warnings but that was bundled with the v1 release with a lot of other changes. |
|
bump! |
|
This is another PR aiming at the same issue #122 |
|
Confirming this fixes #106. /cc @JedWatson |
|
react-codemirror2. Help me build it however we want. Let's move on - we've been waiting months. Why are you all still holding out? |
|
Maybe his subscription here is off, so I felt free and asked him directly: https://twitter.com/In0as/status/896357219473780737 |
|
🌷 👍 🌹 |
windhamwong
left a comment
There was a problem hiding this comment.
Tested out and this works perfectly.
|
@JedWatson bump <3<3<3 |
|
@devonbl react-codemirror2 <3<3<3 |
|
So the thing is: 1. Can @JedWatson review and merge; Alternatively give @skidding merge privileges?2. If not 1. - Can we agree on one fork and move the community over there and continue over there? Also please deprecate react-codemirror?3. Candidates
|
|
Edit: Please try https://github.com/scniro/react-codemirror2 instead. |
Fixes #106