Frontend (React) Routing

[martinpovolny]

• convert/wrap all shared layouts in a React component
• provide support for marking controllers/actions "frontend-routed" on the ruby side
  • full reload = serve just empty layout with menus etc., let react router deal with the rest
  • partial reload/screen change = handled entirely by react router (browser router)
• deal with the edge cases of transitioning between frontend-routed and backend-routed screens
• convert at least one controller to that model (v2v might be good candidate because partly there)
• define a nice declarative route specification, including url (with matching), layout, accordion & tree, bottom toolbar (shown/hidden, gtl vs form buttons), top toolbar probably, and the "center" component (such as a data driven form :))
• have a js dir with just the list of all the screen definitions in a hierarchy

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 6 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions!

[himdel]

related to #6724 and #6327