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
The fn.fetch method returned from the fetch$ function, as described in the README says: "In this case, only the request object is passed as the first argument".
The type signature for the fn.fetch method in the README is as follows, which seems to match the description:
fn.fetch(request: RequestInit,)=>Promise<Awaited<ReturnType<T>>extendsJsonResponse<infer R>
? R
: ReturnType<T>>
But the Arguments section beneath suggests it still takes a payload and an options: { request }, similar to the fn function.
I might be misunderstanding this, but it doesn't seem to match.
Describe the bug
The
fn.fetch
method returned from thefetch$
function, as described in the README says: "In this case, only the request object is passed as the first argument".The type signature for the
fn.fetch
method in the README is as follows, which seems to match the description:But the Arguments section beneath suggests it still takes a
payload
and anoptions: { request }
, similar to thefn
function.I might be misunderstanding this, but it doesn't seem to match.
Your Example Website or App
https://github.com/TanStack/bling#returns
Steps to Reproduce the Bug or Issue
fn.fetch
return methodExpected behavior
As a developer reading the documentation, I expect the arguments to reflect those shown in the types.
Screenshots or Videos
No response
Platform
N/A
Additional context
No response
The text was updated successfully, but these errors were encountered: