1st argument changes, remove "path" and "url" options, bug fixes - #251
Conversation
|
Hey Alex! Thanks for your work on this! I used this library for a toy project over the weekend and it was fairly seamless. I saw in the issue thread that sparked this your consideration of a I have a slight preference for a |
|
@JonKrone I've been doing a lot of research on all the various patterns people use. It seems swr and react-query are blocking fetches with a |
|
@JonKrone After looking at it more, seems like @apollo/react-hooks has significantly more downloads and significantly more people using it. I might do the |
|
I wish there was a way to crowd source people's opinions on this. |
|
I found a way to crowdsource people's opinions on reddit. See the poll here on whether to use |
|
Going to let more people vote before adding conditional auto-managed state. Gonna get these fixes in now though. |
Summary
pathandurlfields in exchange for the 1st argument handling both. Auto managed useFetch doesn't append URL to provider聽#247BREAKING CHANGE 馃毃
Fixes issue when overwriting global options, it changes for every instance of useFetch. Deleting a global option persists for all instances聽#250
fixes the pagination issue here loading bug with cache?聽#237 but might not fix the
loadingbug.small bug fix with
responseTypeTodos
useFetch('path')without the/in the path (might be fine with the current tests)pathto explain how the new way workspathandurloptions. I think it's just this one and this one