You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't like the way I have to update my search parameters when having a search state with more than one property. navigate({ search: (prev) => ({ ...prev, tab: tvalue, }) })
Is there an idea for a better solution or is it an option to modify the update behaviour of the navigate state, so that by default only the state passed is updated? When I want to set my state to null or undefined, I want to do that explicitly.
What are your thoughts about this behaviour? Better solutions are welcome :)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I don't like the way I have to update my search parameters when having a search state with more than one property.
navigate({ search: (prev) => ({ ...prev, tab: tvalue, }) })
Is there an idea for a better solution or is it an option to modify the update behaviour of the navigate state, so that by default only the state passed is updated? When I want to set my state to null or undefined, I want to do that explicitly.
What are your thoughts about this behaviour? Better solutions are welcome :)
Beta Was this translation helpful? Give feedback.
All reactions