quisi.do

I don't think it is currently optimized to handle multiple fetch requests _simultaneously_, but they should be able to dispatch _sequentially_ by just using the hook twice. ```JavaScript const x...

I'm not opposed to `useFetch([])` syntax. I'll add it to the backlog behind launching [ReactN](https://github.com/CharlesStover/reactn) 2.0.

An oddity about this syntax: how do you specify parameters? ```JavaScript useFetch([ './path.json', './path2.json', ]); ``` But now I want RequestInit or lifespan on the fetch requests: ```JavaScript useFetch([ './path.json',...

There are no plans for it currently. I think with concurrent React _hopefully_ so close to launch that they will cover this use case. Concurrent React will likely render this...

A good solution may be to move `@types/react` to a peer dependency that supports either 16.x or 17.x, as bumping it to 17.x could be a breaking change for users...

Anything marked [help wanted] is for grabs. I'm not sure the solution to this though! I think the goal is for 3.0 I'll drop the decorator support and not try...

Thank you for the great idea. `addCallback` is your best bet. It does not currently support the functionality to subscribe a single property. This middleware between the callback and your...

The only time this would be a problem is if you copied the object/array but did not change any values. A reference of an object to itself is considered equal....

Thank you very much for the contribution. I hope others find it and resolve their similar issues. I'll leave this open as a note for the official implementation, but I...

Hi @theKashey, The Object key listener is deliberately shallow. Can you elaborate on the performance issues that you believe this to cause? I am aware that it will cause re-renders...