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
Using the exported fetch and fetchJson methods with a param property in the init object should result in the passed parameters to show up as query parameters in the URL.
The example above results in a request made to /example without any query parameters.
The fetch and fetchJson method exported from the Ajax method doesn't use the params property that's passed through the init parameter. The property is set to the Request object that's created, but the native fetch method in the browser doesn't use the property (neither is it in the documentation for a Request object).
Here's how it's currently implemented in the Ajax class.
Expected behavior
Using the exported
fetch
andfetchJson
methods with aparam
property in theinit
object should result in the passed parameters to show up as query parameters in the URL.Actual Behavior
The example above results in a request made to
/example
without any query parameters.The
fetch
andfetchJson
method exported from theAjax
method doesn't use theparams
property that's passed through theinit
parameter. The property is set to theRequest
object that's created, but the nativefetch
method in the browser doesn't use the property (neither is it in the documentation for aRequest
object).Here's how it's currently implemented in the Ajax class.
In the
cacheManager
class there's mention of astringifySearchParams
method, but it isn't called when a request is made or intercepted.Additional context
Latest version.
The text was updated successfully, but these errors were encountered: