The SAGE2 Webview Container lets you hook into SAGE2 App state while developing an app just as you would develop a normal webpage. For general information, view the guide in the link above.
This repository provides an example of how to do create an app using the SAGE2 Webview Container and React. There are a few main things to note to ensure that your React app works with SAGE2.
- Add the
"homepage": "."
field to your package.json file to make sure resource paths are correctly prefixed - Include the
SAGE2_AppState.js
file found in this repository and load it usingrequire("./SAGE2_AppState.js")
within your application entrypoint - Include the
useSAGE2AppState.js
file found in this repoository and wrap your application in theSAGE2App
component (exported fromuseSAGE2AppState.js
) - Set the initial state values on the
SAGE2App
component using theinitialState
prop (as seen in src/App.js) - Read your entire App state using the
useSAGE2AppState
hook (exported fromuseSAGE2AppState.js
) - Read and write your entire App state using the
useSAGE2AppStateValue
hook (exported fromuseSAGE2AppState.js
)
- Download the skeletonWebviewApp template and follow the instructions in the section titled Step by step on how to use the container for your own application
- Add any state values you declared in the
initialState
prop to theload
section ofskeletonWebviewApp/instructions.json
- Build your React app (using
npm run build
) and copy the contents of thebuild
folder into thewebpage
folder of the skeletonWebviewApp
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