Fixes#269
Options are now re-evaluated when they change, which can be used to change the behavior
of the component where the hook is used based on internal component state.
For example, the `manual` option could be initially true and then set to false based on
the value of a state property, causing the request to fire when this happens.
Similarly, the `useCache` option could be set to true (its default value) then to false
based on a condition, forcing the next request to skip the cache.
Check out [this example](https://codesandbox.io/s/axios-hooks-options-change-v23tl)
and the docs for additional information.
BREAKING CHANGE:
This release introduces a fundamental change in the caching mechanism.
The main difference is that requests that don't use the cache
will store the response in the cache anyway, making the behavior
of the library more intuitive and predictable.
In other words, `{ useCache: false }` will only skip _reading_ from the cache,
but it will write the response to the cache in any case.
The docs contain a caching example providing a full overview of
how the new caching behavior works.
A potential side effect of the new behavior, which we tried mitigating,
is that the `refetch` function returned by the hook, which was always
skipping the cache previously, now stores the response in cache.
Because of this, it must generate a key for the cache, which is created
based on the configuration provided as the first argument to the `refetch`
function itself.
Because the `refetch` function is often provided directly to DOM event handlers:
```
<button onClick={refetch} />
```
this would no longer work because the first argument will be the React event and
we cannot generate a cache key from that, and it wouldn't make much sense either.
Because this is a fairly common scenario, we implemented a specific handling for
this case. If the first argument is an event, it is ignored and considered as if
no configuration override was provided.
fixes#250
This will make it possible to pass the refetch function down to children component and let them
invoke it, without erroring on a missing token.
New behavior: cancelation errors are thrown for requests generated by the `refetch` function.
This is more consistent with how response and other errors are returned when fetching manually.
This feature introduces the ability to disable caching
entirely when using `configure` or `makeUseAxios`,
by setting the `cache` option to false:
```
// with configure
configure({ cache: false })
// with makeUseAxios
const useAxios = makeUseAxios({ cache: false })
```
fixes#199
