4 ms·
Author here - comments and feedback is highly welcome! :)
by chris_engel 8y ago
Author here - comments and feedback is highly welcome! :)
- rajington 8y agoVery intelligent approach! JSX for routes always seemed weird. I especially like the explicit url parameter passing vs. others where it just magically shows up in your component.
- chris_engel 8y agoThanks a lot! That also was one of the main issues I had with React Router and Reach Router.
- dgivney 8y agoComing from a web background, this approach makes a lot of sense to me. Thank you, I'll definitely take it for a spin.
- jcovingt 8y agoThis seems pretty straightforward. I get worried about the complexities of nesting routes, but then I have a fairly simple use-case anyway so I doubt I'll get into the weeds. Similar to another commenter, it never seemed quite natural to me to define routes in jsx. Your solution looks more like a server-side routing table and I appreciate that!
- mwilliaams 8y agoJust finishing integrating hookrouter into my current project. I like it a lot so far! Very easy to implement and reason around. On a certain page my user is filling out a form, and I want to confirm before they can leave, to prevent loss of unsaved data. I think it would be better if this was baked into the package somehow. I'd want something simple where you could set it for a whole page and it applies to children and parents. I also would prefer to be able to pass any function, in case window.confirm() isn't good enough.