[Issue #236]: Server action example

rylew1 commented 1 month ago

Ticket

Resolves #236

Chose the useFormState method (instead of just assigning the server action function to the action attribute of the form) . I believe this is a little more clear to handle returned data and possibly validation errors
I did not tie into an actual API call - though we could add as a follow on maybe (as described here https://github.com/navapbc/template-application-nextjs/issues/116)
Believe we could use useOptimistic in the example to show, for example, show optimisticName immediately, then a serverActionReturnedName when the server action completes
the example uses native form instead of USWDS <Form>. The USWDS <Form> requires an onSubmit handler
For loading you might be able to tie in useFormStatus / pending state

github-actions[bot] commented 1 month ago

St.^{:grey_question:}	Category	Percentage	Covered / Total
🟢	Statements	93.1%	81/87
🟢	Branches	82.35%	14/17
🟢	Functions	93.33%	14/15
🟢	Lines	93.59%	73/78

16 tests passing in 5 suites.

Report generated by 🧪jest coverage report action from 7eeaf44589f4cfeda83c5145667950e7e71af661

rylew1 commented 1 week ago

Also should this be in the nav? Not sure if in general we want the nav to just dynamically include all routes