React Migration: Routing library

[arikfr]

As we're dropping Angular, we need to pick a new routing library. Some of the options are:

• react-router
• Buttermilk
• Universal Router (blog post)

[arikfr]

Maybe Next.js is also an option?

[arikfr]

Out of the 3 t looks like Universal Router is the way to go (great find, @kravets-levko!). Aside from being focused and simple it has some interesting features for us:

• Ability to set baseUrl might help us get rid of a separate index.html file when running in MUTLI_ORG mode (and remove the need to have server rendering of the template).
• Middleware approach will allow to have extensions to the routing logic in a clean way (helpful to implement custom SaaS logic around account status).

It seems like we will have to replace all of our <a> tags with custom ones to use the History API. I think Angular's router does it differently by having some listener on <a> tags events? @kravets-levko do you know?

[arikfr]

Yep, Angular has a click listener on the root element. The only reasons I see to replicate a similar logic:

• Avoid having to search and replace existing <a> tag usages with the new tag.
• Have generated links in query results to other queries/dashboards work with internal navigation instead of invoking full page refresh.

Not sure it's worth it.