-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NPM Module for managing application flow as state machine #17
Comments
Leaving a couple of drive-by thoughts here: |
@KevinJBoyer PFML we'd probably be using xstate library similar to PFML, so i guess i wouldn't really consider that particularly custom. i haven't seen any library that captures the higher level need — i think treating application flow as a state machine is maybe still somewhat niche. in any case, i agree that we need to flesh out and refine the design, which should be part of the work for this ticket. |
More complex user-facing applications, especially ones that intake claims/applications/cases often need to manage the application flow. A best practice is to manage this with a state machine and abstract it into a flow management module. This approach also provides useful product development tools like visualizing the application flow as a flowchart diagram.
This issue is to capture the idea of making a reusable module for this functionality. The current vision for the implementation approach would be to implement this as a separate npm module, and it could be imported by default in https://github.com/navapbc/template-application-nextjs. That would make it easier to rip out than if the code was baked into the application template itself.
Scope
Scope of this ticket should include designing the npm module (e.g. in a tech spec) prior to implementation
The text was updated successfully, but these errors were encountered: