4 ms·
(Not OP) The kind of regressions I'd think of would be things like: - updating the URL state when someone clicks on a button - proper back-button support in t
by dkyc 3y ago
(Not OP) The kind of regressions I'd think of would be things like:
- updating the URL state when someone clicks on a button
- proper back-button support in the browser that takes me back to the prior 'page'
- being able to navigate to any URL deep in your app and get a valid response (ideally rendered server-side so there's no client-side loading delay).
Things like these are hard, and the reason why it's common advice to use a framework and not hand roll. If you hand roll but don't support these things gracefully, you're making a case for not hand rolling.
- Garvi 3y agoTrue. One needs to build it's own "router" if you will. But in practice that means writing functions that modify the URL (some pushState(url) and scrollTo(top) stuff) and make them part of the primary function, so you can forget about it (I'm a functional programmer). Same with adding/substracting from the history stack. 1h of work each. Is that too much? It really just worked without much troubleshooting. Most trouble I've had was with cookies and cross-origin problems (or weird client requests).