warn if mis-match dynamic node registered about routing-kit HOT 3 CLOSED

I wanted to open an issue for discussion similar to this so might as well do it here. I wanted to recommend that upon registering a new route, router issues a fatal error in case it concludes there is an ambiguity. Router has no way of making a valid decision on what should be done, and this happened because of a programmer error which I think should crash on boot.

from routing-kit.

This is a limitation of the design of the router. A given node can have at most one wildcard child. In the above example, there is no way to distinguish between an Order and Order.ID component.

Since the Order component is registered first, the router node is set as "order" type. When the second route is registered, the router sees a parameter path component is already there and uses that. There is no check as to whether the existing parameter type is the same.

A suggestion could be printing a warning (and perhaps failing) if non-matching paramater type path components are registered to the same node. This could be done here.

from routing-kit.

This should be possible by adding a check that, if a dynamic child node already exists, its value is equal to the new dynamic node's value.

from routing-kit.