d740518e75
1. It's not just processes, it contains the list of all DMN Decisions as well. 2. It is closely linked to the SpecReference object that can be generated by looking through all the Spec files to find the processes and decisions they contain. 3. It is a cache of information, the file system is the source of truth. Seems likely we will cache more things in the future -- so setting things up this way made sense. |
||
|---|---|---|
| .. | ||
| .github | ||
| bin | ||
| cypress | ||
| public | ||
| src | ||
| .eslintrc.js | ||
| .gitignore | ||
| .prettierrc.js | ||
| .tool-versions | ||
| Dockerfile | ||
| LICENSE.rst | ||
| README.md | ||
| craco.config.js | ||
| cypress.config.js | ||
| docker-compose.yml | ||
| package-lock.json | ||
| package.json | ||
| sonar-project.properties | ||
| tsconfig.json | ||
README.md
spiffworkflow-frontend
NOTE: This is still in development. NOT READY FOR GENERAL USE!!!!!
This is the frontend part of an app that leverages spiffworkflow for managing and running business processes. The backend portion can be found at https://github.com/sartography/spiffworkflow-backend.
This project was bootstrapped with Create React App, and the balance of this README contains information about how to use apps that are bootstrapped with that project.
Available Scripts
In the project directory, you can run:
npm start
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may also see any lint errors in the console.
npm test
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
npm run build
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.
npm run eject
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.
npm run lint
Check for lint in code.
npm run lint:fix
Fix lint in code.
npm run format
Probably just stick with lint:fix which also runs prettier.
Learn More
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
Code Splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
Analyzing the Bundle Size
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
Making a Progressive Web App
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
Advanced Configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
Deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
npm run build fails to minify
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify