Open luissmg opened 5 years ago
seems like instead of unsetParams we should just change getParam so that it considers undefined to be empty
Yes, that is a good alternative. Or when you set something to undefined
it unsets the parameter. Maybe your approach is better
I searched a lot for this and didn't find anything regarding what I am about to write. Sorry if I missed any open issue about this.
Context
Let's consider the case where when I show some random component I set a param and I read that parameter in, let's say, the appbar.
Component setting the param:
Component reading the param:
As you can see, when I don't set the param I use a default value using the
getParam
function on thenavigation API
.Problem
In the first same component, when I unmount it I want to restore the default value. BUT I don't want to set the param again with the default value because I am using
getParam
form that. I want to unset that param. Setting the param toundefined
does not work.Solution
Maybe implement a
unsetParams
function to unset parameters from the navigation state.