Possible collision with a future built-in React API

[just-boris]

React is going to introduce concurrent mode which will include a new useTransition hook. However, this library provides a hook with the same name, which is an unfortunate naming collision.

Do you have any ideas or plans how to deal with that?

I opened an issue in the react repo already: facebook/react#17190

[danielkcz]

Just my 2 cents, I don't think this is a problem. You have plenty of hooks out there with colliding names already, not only against React codebase. I don't think those should be renamed just because React adds something with that name later.

I have seen it in other codebases and we (our team) adopted it as well ... just React.useTransition and you are golden. I recommend prefixing all React hooks like that.

[drcmda]

i agree, and ultimately i hope they're taking that burden off our shoulders: reactjs/rfcs#128 in any case, i think for us useTransition makes perfect sense, but in reacts case, having to do with suspended fallback mechanisms that name was such an odd pick. i don't we should be compelled to just use a worse name for what in fact are actual transitions.