James, great work!
I’ve had similar thoughts for awhile re react router and the like, and really appreciate your breakdown of the issues. I’ve been using Redux First Router for a bit and it’s been great, conceptually it fits so well with Redux and is otherwise not in the way!
My only qualm is the decision to not support query parameters. I understand that for SEO they are not ideal but there are definitely some valid use cases for them on the web.
For example, let’s say I have a search page with a few filters the user can tweak AND I want to expose the URL for a particular search to the inter webs, that is, have a link on some other page that goes directly to the search with the appropriate criteria. There are definitely ways to do this without query parameters, such as encoding the criteria in a URL parameter(s) but they seem a bit hacky. I’m not sure that URL parameters do a great job of handling a dynamic set of key-value pairs.
While I would love for support for query parameters to be added, I’m also interested in the discussion and any thoughts you have in potential solutions. To me, they seem to be a vital part of the web, and a missing feature despite the current fantastic feature set of RFR.
In the meantime, I just rolled my own conceptual knockoff that still leverages Redux First Router Link!
Love to hear your thoughts
Dave
