Skip to content
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

Fix form errors and styling on rate details page #2395

Merged
merged 5 commits into from
Apr 30, 2024

Conversation

JasonLin0991
Copy link
Contributor

@JasonLin0991 JasonLin0991 commented Apr 30, 2024

Summary

Fixed form errors not showing up and some styling.

Form Errors

  • Slack about form errors

  • under actuarial firm if I select "other" the validation error "you must enter a description" appears right away. It should only appear after I hit continue

  • If I am missing a form field in the additional actuaries and try to continue, I get only line item errors. I am NOT seeing the error appear within the error summary banner at the top like I would expect.

  • I also find "remove" to be vague given all the competing links. I would suggest "remove certifying actuary" or something like that. (there are a lot of links, something for Kelsey to noodle on I think, but not a blocker)

UI styling

  • Figma
  • Fixed spacing on the Remove certifying actuary button

Related issues

Screenshots

Test cases covered

QA guidance

@JasonLin0991 JasonLin0991 marked this pull request as draft April 30, 2024 16:47
@JasonLin0991 JasonLin0991 marked this pull request as ready for review April 30, 2024 16:51
@JasonLin0991 JasonLin0991 requested review from haworku, macrael, ruizajtruss and pearl-truss and removed request for haworku and macrael April 30, 2024 16:51
@JasonLin0991 JasonLin0991 merged commit 02f1144 into main Apr 30, 2024
28 checks passed
@JasonLin0991 JasonLin0991 deleted the fix-form-errors-on-rate-details-page branch April 30, 2024 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants