Will fetch data from the endpoint provided, and expose such via context.
Has support for reading/writing from the browser cache using several strategies.
This component will NOT manage your cache lifetime.
<FetchContext
cacheName='todosAppCache'
cachingStrategy='networkFallbackCache'
defaultData={{
userId: 0,
id: 0,
title: 'Example Todo',
completed: false
}}
request={new Request('https://jsonplaceholder.typicode.com/todos/1')}
>
<RenderJSON />
</FetchContext>
git clone git@github.com:tonytino/FetchContext.git &&
cd FetchContext &&
npm install &&
npm start
App.js
is already configured to demo all four caching strategies. Try testing
out the functionality by running through this flow:
-
Turn off WiFi and load page
Default data should be loaded only.
-
Turn on WiFi and load page
Network data should be loaded only.
-
Turn off WiFi and load page
Cache and default data should be loaded only.
Default data will be loaded where
cachingStrategy = 'network'
. -
Turn on WiFI and load page
Network and cache data should be loaded only.
Cache data will be loaded where
cachingStrategy = 'cacheFallbackNetwork'
.Cache data will be loaded temporarily where
cachingStrategy = 'cacheThenNetwork'
; you can see this by throttling your network speed toSlow 3G
in devtools).
fetch
may not be supported in all environmentscaches
may not be supported in all environments- Cache lifetime is not managed
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build
folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject
, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject
at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject
will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject
. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify