mirror of
https://github.com/status-im/react-native.git
synced 2025-01-10 01:25:39 +00:00
88ebdb2a65
Summary:This makes the `refreshing` prop more 'controlled'. Before forgetting to set the refreshing prop in the onRefresh callback would make the js and native `refreshing` prop get out of sync and make the RefreshControl stop refreshing properly (see #5839). I also added a simple usage example and a note about the refreshing prop in the doc. There was also a small bug in the doc generation code that made the array of color show as [[object Object]] instead of [color] so I fixed that too. ** Test plan** Tested using the UIExplorer example on iOS and Android. Not setting the `refreshing` prop to true in the `onRefresh` function should cause the RefreshControl to stop refreshing immediately and continue working properly after. Closes #5839 Closes https://github.com/facebook/react-native/pull/6434 Differential Revision: D3046279 Pulled By: nicklockwood fb-gh-sync-id: ebda04c659a10f0b9d468473c8d5c659256ca1b5 shipit-source-id: ebda04c659a10f0b9d468473c8d5c659256ca1b5
Run the website server
The first time, get all the dependencies loaded via
npm install
Then, run the server via
npm start
open http://localhost:8079/react-native/index.html
Anytime you change the contents, just refresh the page and it's going to be updated.
Publish the website
cd website
npm run publish-website