add formValues and formErrors to /current-name

[Fbasham]

Summary

EDIT: I now realize there are more routes that need the implementation...I wonder what other TS errors are making this a pain.

I think we can all agree TS is a pain sometimes. Originally we had partially agreed to remove the persistent error messages/partial validated default form values on language toggle. Instead of completely removing it, why not instead make it work for the route that didn't have this feature? If it's still a flop, let's remove it completely.

Types of changes

What types of changes does this PR introduce?
(check all that apply by placing an x in the relevant boxes)

• 🛠️ refactoring -- non-breaking change that improves code readability or structure
• 🐛 bugfix -- non-breaking change that fixes an issue
• ✨ new feature -- non-breaking change that adds functionality
• 💥 breaking change -- change that causes existing functionality to no longer work as expected
• 📚 documentation -- changes to documentation only
• ⚙️ build or tooling -- ex: CI/CD, dependency upgrades

Checklist

Before submitting this PR, ensure that you have completed the following. You can fill these out now, or after creating the PR.
(check all that apply by placing an x in the relevant boxes)

• code has been linted and formatted locally
• added or updated tests to verify the changes
• added adequate logging for new or updated functionality
• ensured metrics and/or tracing are in place for monitoring and debugging
• documentation has been updated to reflect the changes (if applicable)
• linked this PR to a related issue (if applicable)

Linting and formatting

npm run lint:check
npm run format:check

Unit and e2e tests

npm run test
npm run test:e2e

Additional Notes

If this PR introduces significant changes, explain your reasoning and provide any necessary context here. Feel free to include diagrams, screenshots, or alternative approaches you considered.

Screenshots (if applicable)

Provide screenshots or screen-recordings to help reviewers understand the visual impact of your changes, if relevant.

[gregory-j-baker]

Adding this to all the routes might be okay with the current implementation (where we store the validated data in the xstate machine).

When I originally tried this I first started by modifying what data was being stored in the machine, and that change quickly snowballed into typescript hell when I tried updating the error stuff.

[Fbasham]

Adding this to all the routes might be okay with the current implementation (where we store the validated data in the xstate machine).

When I originally tried this I first started by modifying what data was being stored in the machine, and that change quickly snowballed into typescript hell when I tried updating the error stuff.

Yeah. When I first opened this PR I though this was the only route missing the implementation after looking at the state machine. Didn't look closely into each route though. If I have time I'll look into adding the rest.