Pablo Palacios

@ljharb I can close this PR and post the branch in the other one, no problem. Regarding applying the changes in the 16.3 adapter: does it make sense? React just...

I like the idea of moving everything to just one object. In the future, the `resource` property could also accept an array of resources so we could trigger many requests...

By the way, these are all the options that we "support": ## Global options ```js const fetchr = new Fetchr({ corsPath, // string, path to be used in case clientConfig.cors...

My proposal: ```js const proposal = { path, // string, replaces xhrPath, corsPath and uri urlBuilder, // function, replaces constructGetUri headers, context, // object|function, replaces contextPicker timeout, statsCollector, usePostOnRead, //...

I would then rename it to `url` (this is the argument name in mdn for XMLHttpRequest.open). Currently it's either one or another: https://github.com/yahoo/fetchr/blob/master/libs/fetcher.client.js#L236 and they are never concatenated. Since `XMLHttpRequest`...

Besides changing the request object, I think it would be very cool if we could let the users name the operations. We could use POST by default and add an...

> the user can always organize the fetchr to use any number of methods @redonkulus Is this possible right now?

@ljharb I finally had time to take a look a this one again. I was able to make the missing test to pass. Could you review it again?

Cool, let's go step by step. Important tests that we should have: - It registers/unregsiters to the given store - It updates when the store is updated You can take...

@redonkulus I do. At work we are using 2 custom hooks for stores: `useStore` and `useStoreSubscription`. The difference is that the later one subscribes to changes for the given store...