You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any reason why docuri has to store everything in the global state risking conflicts between different parts of the application? Consider the alternative API with no global state:
varroute=docuri.route('/foo/:bar/');
If the user wishes to store his routes in a global map, he is still free to do so, but he doesn't need to.
This addition is even backwards compatible, if we inspect the absence of name parameter.
I would, however, also recommend to promote this as the primary way to use the library.
The text was updated successfully, but these errors were encountered:
This breaks backwards compatibility.
This removes .routes because it's not intuitive what the result value
of that must be, and users are free to .map over .route themselves.
Also, .routes was never tested.
Fixesjo#14.
Is there any reason why docuri has to store everything in the global state risking conflicts between different parts of the application? Consider the alternative API with no global state:
If the user wishes to store his routes in a global map, he is still free to do so, but he doesn't need to.
This addition is even backwards compatible, if we inspect the absence of
name
parameter.I would, however, also recommend to promote this as the primary way to use the library.
The text was updated successfully, but these errors were encountered: