archive-gh-me/axios-cache-interceptor
1
0
Fork 0
mirror of https://github.com/arthurfiorette/axios-cache-interceptor.git synced 2025-12-08 17:36:16 +00:00
Code Issues Projects Releases Wiki Activity

docs: spelling

Browse Source
This commit is contained in:
arthurfiorette 2022-12-26 11:38:04 -03:00
parent 79ac027262
commit db41b7c7cc
No known key found for this signature in database
GPG Key ID: 9D190CD53C53C555
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/src/guide.md
View File

@ -30,10 +30,10 @@ finally returns the response to the original caller.
- Return previous cached request if the new one failed.
- Handles parallel requests
- 100% Customizable
- Memory, LocalStorage and SessionStorage built-in storages.
- Built-in storages like In-Memory, Local Storage and Session Storage.
- Less than 4.3Kb minified and gzipped.
- Development mode to debug your requests.
- 22 times faster than using axios and 8% faster than axios-cache-adapter.
- 22 times faster than using axios and 8% faster than `axios-cache-adapter`.
- And much more...
## Why not...?
@ -50,4 +50,4 @@ As this library was built to be used with axios and to handle storage itself, I
that it is more performant that any glued code you may find and/or write yourself. About
state management libraries and other similar things,
[this blog post](https://arthur.place/implications-of-cache-or-state) explains why cache
is mroe correct, architectural way, instead of state.
is more correct, architectural way, instead of state.