a71af6e40f
* Update README.md Some notes for people that might want to run full-on native, with detail about how Mac hijacks port 7000 and how to get around it. * Revert "Update README.md" This reverts commit 096887c26d591f93a836ef808c148af09767f2d2. * README update and native code patch Some details for user that might be running Python3, Mac, and want to run everything locally/natively. * Implement basic tooltips Uses MUI tooltip, as it behaves more predictably with existing styling, and enables top-level theme config. Top-level configuration for all MUI components can be controlled via overriding the existing theme. See index.tsx. This could be done per user for customization, etc. Enabling JSON module imports in tsconfig.json seemed to fix the error in ReactDiagramEditor * Naive AI code editor implementation A working starting point. * Implement API to return if script assist should be enabled Along with route and function, api config, etc. * UI calls backend to see if script assist is enabled. If it is, loads the related UI, otherwise it doesn't appear. * Moving forward with service for message processing. * Services scaffolded * Open API called, prompt-engineered to get script only. * Little cleanup work * Enabled + process message working. Had to find all the places permissions are enabled, etc. * Cleanup, comments, etc. * Env vars, styling, error cases, conditional display of script assist Finishing touches for the most part. REQUIRES TWO ENV VARS BE SET. SPIFFWORKFLOW_SCRIPT_ASSIST_ENABLED=["True" | "true" | 1] (anything else is false) SECRET_KEY_OPENAI_API=[thekey] The are retrieved in default.py. I run the app locally, so I just set them in the terminal. NEW INSTALL: @carbon/colors (so we consistently use carbon palette etc.) * Fix tooltips, clean up some styling. Finishing it off. * Add loader and error message Complete UX stuff * Update useScriptAssistEnabled.tsx Remove log * Update script_assist_controller.py Add this tweak to avoid TMI. * Some reasonable changes suggested by the build process * Comments from PR. * Update ProcessModelEditDiagram.tsx Should (but I don't know how to tell yet) call the change handler that wasn't firing before. * updated the permissions setting in authorization service w/ burnettk * precommit now passes. tests are failing w/ burnettk * pinned SpiffWorkflow to known working version and fixed tests. we will update spiff in a later pr w/ burnettk * made changes based on coderabbi suggestions * updated the error handling to be more inline with how we have handled other errors and some ui tweaks * removed pymysql package w/ burnettk * forgot to remove pymysql from lock file w/ burnettk --------- Co-authored-by: Tim Consolazio <tcoz@tcoz.com> Co-authored-by: Kevin Burnett <18027+burnettk@users.noreply.github.com> Co-authored-by: jasquat <jasquat@users.noreply.github.com>
spiffworkflow-frontend
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/spiff-arena/tree/main/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.
Runtime configuration options
The frontend docker image respects the following environment variables.
SPIFFWORKFLOW_FRONTEND_RUNTIME_CONFIG_APP_ROUTING_STRATEGY=subdomain_based SPIFFWORKFLOW_FRONTEND_RUNTIME_CONFIG_APP_ROUTING_STRATEGY=path_based
subdomain_based example: api.spiffworkflow.org goes to backend
path_based example: spiffworkflow.org/api goes to backend
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