I’m trying to find a way to safely modify the routing parameters in an routing pipeline step.
My problem is that I have a page that might require rather complicated activation parameters and those must be configurable and stored in database along with the navigation menu structure.
What I was thinking was to just add a query string parameter to the link (like ?get_config=1) and, in a preActivate step, if I have the parameter, fetch the configuration from the server before forwarding the request with this config added to the parameters that will be passed to the activate method of the viewmodel.
I tried modifying the routingContext in my pipeline step but with no effect on the activation parameters. Aurelia seem to be getting those from another object and I’m not sure if I can safely modify anything in there…