useTransition hook name already exits in the ecosystem

The new concurrent mode provides a new hook - useTransition. However the name of it is confusing. The word “transition” in web development already refers to animations and css transition property. There also exist useTransition hook provided by react-spring library. So people who will use both concurrent mode and react-spring in their projects will be confused by clashing names.

Did you consider different names for concurrent transitions? For example, useTransaction is not present in the ecosystems and can be used to describe concurrent updates.

[just-boris]

@FredyC

However, I don’t really have a better one. Does either one of you have some idea?

I proposed useTransaction in my initial comment. It fits into my mental model of concurrent mode pretty well

[eddyw]

Does either one of you have some idea? Let’s provide constructive criticism, please.

All this just came to my mind: useParallelUniverse 🙈 (from docs examples) useConcurrentTransition (too long?) useTransit 🤔 useFork (it refers to a “forked” tree) useConvergence useStage (like staged environment)

The naming useTransition may make sense but there is also react-transition-group besides react-spring, you may end up with:

React.useTransition Spring.useTransition RTG.Transition

Also, what about tree shaking on an existing lib without side-effects that may already include useTransition?, doing this import * as Lib from 'lib' may cause all exports to be included (Yes, you can alias import { useTransition as useBlabla } from '...' but that’s not the point)