TL;DR generate changelists of app state mutations that can be used in cases where it's necessary to be able to predict what will happen when some action is invoked, e.g. linking into another route.
I've had this zany idea floating around that I just wanted to share that's probably extremely over-engineered to over-solve problems in the routing domain, but I figured I'd share it and see if any lightbulbs go off.
So in routing land, one of the harder things to calculate is a link's href; we have have to use the provided destination rout and the contexts to provide to basically ask "if this transition were to take place, what URL would you end up with?". This has led to some interesting code with query params, particularly with model dep state, where we have to say "given this destination route, these contexts, this list of explicitly provided query params, please fill sensible default values for unspecified query params and tell me what the final URL is going to be".
Particularly in nailing down these last