AsyncMode -> ConcurrentMode

[trueadm]

Follow up to facebook/react#13732. Renames AsyncMode to ConcurrentMode.

[bvaughn]

This will break compat for all existing React releases that use AsyncMode – we'll need to support both.

So like, add the two new constants, and update the case statements so that async+concurrent mode both follow the same path, etc.

[trueadm]

@bvaughn I thought that was the point here? It's an unstable API so can break in any version, right? I'm happy to add support in on the devtools, but the PR to rename AsyncMode has already landed in React – did you want me to revert it?

[bvaughn]

@bvaughn I thought that was the point here? It's an unstable API so can break in any version, right? I'm happy to add support in on the devtools, but the PR to rename AsyncMode has already landed in React – did you want me to revert it?

Well, yes– the API can change in that we can e.g. rename the export with a new release of react but we don't want a DevTools update to break compatibility with older releases. (DevTools tries to be compatible with all previous React versions.)

So in this case, we'll need the 16.x DevTools adapter to handle both AsyncMode and ConcurrentMode types. 😄

[bvaughn]

This isn't sufficient. We need the number and string.

[trueadm]

The number is the same though?

[bvaughn]

Haha, d'oh! Ok sorry.

[bvaughn]

I think this looks right 👍 Would be nice if you could give it a quick test with the existing release of React, as well as a build from master.

[quantizor]

It'd be cool if you reviewed my PR from 2 weeks ago that has its corresponding change already in react core and released. Thanks.