Sophie Alpert
Sophie Alpert
cc @salier :) – What should we do here?
None currently – this is not a high priority for us right now. I'd be happy to look at a pull request if anyone dives into fixing this.
It hasn't been a high priority because onChange firing too frequently rarely causes problems. Where is it causing problems in your app?
Would it be better to warn when rendering \ without a \ child? eg for \, we require a \ component to be explicitly rendered, rather than attempting to recover...
Given the async nature I guess the warning could be for a \ without a \ then. Though I thought that typically the whole shell would come in at the...
Interesting bug, thanks for reporting.
It seems like for the spellcheck case we could do a "diff" of the old and new strings within a block to infer the change – even just stripping off...
> MO worked okay for the most part, but was a **huge** headache for handling Apple autocorrect. Why was that?
I just typed ``` hello, here is a banana ``` in Google Docs then backspaced "banana" and changed it to ``` hello, here is an orange ``` in another window....
I don't think it's practical for us to use `const` in what we ship unfortunately. This is interesting though…