The point is not to introduce any new concepts, so as much as possible Redux-First Router is familiar to users experienced with Redux.
So I don’t agree. It was a carefully chosen name that has been clicking with people. In fact it was something else “domain-specific” back in ancient history, just like you’re saying.
There’s a million libraries under the sun that all come up with some new callback name: onMount, onRouteWillMount, onBeforeBlaBla. My opinion is nobody needs more names to remember, when what this is, is exactly what is: a thunk.
In short, rather than be bogged down with either the “WHAT” or the “HOW,” the “WHY” (the most important question) is one that has already been answered for you by virtue of identical terminology. At least you knew exactly why I named it, and therefore WHAT it was and HOW it works. The lower you go, the more benefits you provide to all, and again WHY is the lowest question, the root.
But I do hear you on the domain language. The reality is that time has come and gone, thunk as useless as it otherwise is has become meaningful. Truthfully there’s tons of lingo surrounding Redux that I’ve long accepted — i still call actions, action creators, thunks, all just actions. I wonder what a renamed Redux ecosystem in an alternate reality would look like…I agree, it could have done better with better domain terminology and less bloat, but I think the naming chosen at this juncture is what will have the most impact :)
