When it comes to implementing a url-based Router
(aka Nav2) there are really 2 high-level components to the API:
- A controller to read/write to the current url
- A parsing/matching system to convert a url into a stack of views, or pages.
The interesting thing here, is that the controller portion, is a fairly stable, boring API. Reading or writing the url
location, or accessing queryParams
is all pretty straight-forward. Really all you are doing here is setting a string value, and parsing query params using the URI
class.
Continue reading →