Make debounce specific to the instance

[sslotsky]

Solution to #47, ensures that the debounce is applied at the instance level. The way it is currently written, all instances of this component are sharing the same debounce so only one instance will update when multiple instances on a page are supposed to update simultaneously. This is an issue for things like drag & drop sorting of codemirror content blocks.

[sslotsky]

Should also mention this. My app did not complain about ref="textarea" when I was using the npm package, but as soon as I ran npm link to my local copy, I started getting the "Only a ReactOwner can have refs" issue. My understanding is that this way of using refs is preferred anyway so hopefully it's not a problem to make this change.

[sslotsky]

Any chance of getting a review on this?

[attaboy]

Just a note that I've also stumbled on issues caused by #47 too — my first instance of CodeMirror on a page doesn't keep its options in sync with state when there is another instance on the page too.

This pull request solves the problem for me.

[nm2501]

I can vouch for this PR too. I have several Codemirrors on the same page and modifying the 'value' (i.e. the code within the textarea) was only working for the bottom instance. With this PR, it works for all instances.

Thanks @sslotsky

[sslotsky]

@JedWatson Any chance of getting this PR reviewed?

[erik-sn]

This also fixed an issue I was having with redux state not updating multiple mirrors.

Thank you @sslotsky - @JedWatson you should consider merging this one.

[veeramarni]

I agree with @sslotsky the ref string attribute is gone in version 0.15.0 and you need to use ref callbackup attribute.

check here

In render function

        return (
            <div className={editorClassName}>
                <textarea ref={(ref) => this.textarea = ref} name={this.props.path} defaultValue={this.props.value} autoComplete="off" />
            </div>
        );

in ComponentDidMount

 componentDidMount () {
        const textareaNode = this.textarea;

[tonyonodi]

I was having the same problem where the value wouldn't update as @nm2501 and this fix worked for me too.

Thanks @sslotsky

[rgbkrk]

Hey @sslotsky would it be worth rebasing this?

@JedWatson I'm more than happy to help steward maintenance here as are other folks in the PRs. Let us know if there's a way to resolve (or even close!) these PRs.

[sslotsky]

@rgbkrk I'd be happy to rebase it but I'd be even happier if I had some indication that @JedWatson is aware of this PR.

[JedWatson]

Sorry for the delay on this - I totally missed it (!)

Looks good, would be very happy to merge it if you don't mind rebasing @sslotsky.

[sslotsky]

@JedWatson Sure I'd be glad to rebase it. Would you also like me to undo the changes to lib? It occurs to me that you probably just compile before publishing, and that's why my lib changes included things that I hadn't touched in src.

[sslotsky]

Closing in favor of #68