-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Guest application implementation #610
Comments
Hi @erikguntner this is related to Guest Application Form #533, right? |
@paulespinosa yes |
I see a key feature is being able to save the current state of the form and being able to come back to complete it later. Took a look at our back end and didn't find this capability- endpoints to retrieve the data from the specific user. Also wondering if the questions are made in the front end or brought in through the backend since I saw schemas for |
@JpadillaCoding The backend hasn’t been implemented for this feature. The tables mentioned are from a preliminary design from a while back. It’s likely that the database will be refactored when the backend is implemented. |
Just a rough idea based on the epic and our meeting. Let me know if I'm missing something or need any modification based on the complexity of the ticket items. Also, I think we should write these tickets as we go and we're figuring out what's needed while using this as a rough outlook of the task and things needed.
|
@JpadillaCoding @johnwroge let's discuss where this stands, and whether remaining child items should be rolled into a new issue or appropriate to continue tracking here |
@tylerthome We can still use this for tracking this issue. With Tyler's implementation of the intake fields #672 . We should start making more progress on these items. I believe @johnwroge is using Tyler's intake field branch to make the forms and also I'm currently integrating the buttons onto his branch. |
Overview
We need to ideate, document and review possible approaches to creating application process components
Detail
This issue outlines a possible approach to creating the components necessary for the application process. I'm sure there are many ways to go about this but this is what I came up with after looking at a couple of examples.
The application can be broken down into 3 main parts as seen in the image below:
Implementation details
Regarding parts 1 and 2, you can see that as the user moves through the application each page contains a progress bar and 3 buttons that allow them to navigate the form and save data. Inside that, form elements are switched out based on the route/step the user is on. To accomplish this I suggest creating a wrapping component that controls the process of stepping through the form, a progress indicator, handles the storing, submitting, and validating of all form data, and renders an outlet that swaps out the form content. Using a Formik context we can then access the data values with a useFormik hook. Below I've written some pseudo-code to provide an example:
For the application review page, we can read all data from Formik and render it out in sections with the edit links navigating the users to the corresponding page.
Action Items
Resources/Instructions
https://www.figma.com/file/BNWqZk8SHKbtN1nw8BB7VM/HUU-Everything-Figma-Nov-2022?type=design&node-id=9669-3122&mode=design&t=vslawtLY5SCk56TJ-4
Formik
Formik Context
useFormik
yup
The text was updated successfully, but these errors were encountered: