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
Currently there doesn't appear to be any support for query parameters, i.e. /some-resource/:id/sub-collection?filter=some-facet
Query parameters are different from params because they're optional and often used in GET requests to filter the result in some way.
At present, the library actually prevents query parameter usage entirely, as the client will throw a type error if you try to add one.
A simple solution in the interim may be to add a queryParam object to the request info options object. This could be typed as URLSearchParams so we leverage existing browser implementations.
The text was updated successfully, but these errors were encountered:
Currently there doesn't appear to be any support for query parameters, i.e.
/some-resource/:id/sub-collection?filter=some-facet
Query parameters are different from params because they're optional and often used in GET requests to filter the result in some way.
At present, the library actually prevents query parameter usage entirely, as the client will throw a type error if you try to add one.
A simple solution in the interim may be to add a queryParam object to the request info options object. This could be typed as URLSearchParams so we leverage existing browser implementations.
The text was updated successfully, but these errors were encountered: