mogul
commented
7 months ago Noting here that I stumbled across an RJSF option that might work for that particular team.
If this RJSF adapter pattern generalizes to other languages and frameworks, maybe all that's needed from Spiff is a list of pointers to them in the docs. 🤔
Story
In order to provide workflow services to my app which has a custom frontend, I want spiffworkflow-backend to provide UI cues for jsonschema forms that do not presume any particular frontend language stack or framework is in use.
Background
The form editor and display of forms in spiff-arena's included frontend is based on
react-jsonschema-form. That also means theui-form-file-nameelement you get via the API......is RJSF-flavored.
The problem
Our org operates a bunch of apps using a bunch of different language stacks for their app and different frameworks for their frontend. If you want to integrate SpiffWorkflow's backend with one of these apps that doesn't use React, then there's a pretty big hill to climb.
As an example from one team's perspective: Their app uses Django (meaning, it's written in Python). They need forms that they generate to conform to the US Web Design Standards (USWDS). They can pull in
django-jsonformsand present a form for the jsonschema that Spiff provides for a given task. However, they would not get UI cues from SpiffWorkflow that are useful.Other options
jsonforms.iocomes with bindings for React, Angular, and Vue. The "UI schema" for customizing form behavior is agnostic to which theme is being used. The architecture is conducive to deriving and further customizing forms for specific local needs.json-editor, on which that Django library relies, is itself framework-agnostic while still being friendly to bindings for various language stacks/frameworks (for example,django-jsonformsas described above). I see people have also made bindings for use with React, Angular, Vue, and webcomponents, and themes for various CSS frameworks (Bootstrap, Tailwind, Spectre, etc... though not USWDS (yet)).So: Is there any openness to embedding
json-editororjsonforms.io(or something else that's not framework-dependent) as the basis for forms in the SpiffWorkflow frontend/backend instead of RJSF?