Add modals to the router and history state

[robiningelbrecht]

better approach to suggestion in #240. This will allow users to use the browser "back" button to navigate back to the previous page and/or modal

[robiningelbrecht]

cc arminus

[robiningelbrecht]

@FoxxMD I'd like to have a second opinion (if you have one).

Currently the app has a simple router built in javascript that fetches the main content via ajax when an URI is clicked. The History API manages back and forward navigations. The advantage of this approach is that it's very fast because there's no need to bootstrap Symfony on every new request. The downside is... I have to manage routing, which sucks now that I want to add modals in to the mix.

I'm thinking of starting to use the Symfony routing component. Advantage is that adding modals to the mix is way easier. Disadvantage is that the app will be slower because we need to bootstrap Symfony.

Feedback? :p

[FoxxMD]

My opinion is pretty heavily biased and probably not what you want haha. I always avoid server-side rendering when possible. I like to keep the backend and frontend separate applications whenever feasible to self-enforce clean interface contracts (API) on myself. IMO it always makes inevitable refactoring easier since they aren't tightly coupled.