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
Though to be honest it seems like query params ought to just be handled separately from this library - if it were me I would limit the API surface of this just to route paths, and just deal with search params outside of this library, to contain scope.
The text was updated successfully, but these errors were encountered:
I would tend to agree. I've just chosen to support query now as it was convenient for the project I created the library for. Might make sense to deprecate that functionality. I'll think about it :)
like
/myRoute#some-section
Though to be honest it seems like query params ought to just be handled separately from this library - if it were me I would limit the API surface of this just to route paths, and just deal with search params outside of this library, to contain scope.
The text was updated successfully, but these errors were encountered: