-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggested approach for PUT/PATCH/POST #6
Comments
Thanks! Haven't thought much about this, but I think an API I would like, rather than introducing new root level exports, is something like this:
So the existing API would be unchanged, but we could pass options as a second argument, for instance with a What do you think? |
I definitely like the merging of options - I was thinking the same thing! Not loving the |
Version 1.1.0 addresses this now. More details in the updated docs. |
Thank you! It looks great. |
This package is great - thank you!
Do you have a suggested approach for mutations? Maybe something like
usePost
orusePut
, which might return a function/promise.The text was updated successfully, but these errors were encountered: