You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Veteran, I don't want my first name in the welcome message on the MHV landing page to be displayed in all caps, so that I feel as welcome as intended.
Notes
in demo on 12/17, Kaitlin did a live demo in prod and we saw that her first name on the landing page was all-caps.
also, preferredName is still not preserving user's intended casing. some discovery happened in this slack thread, where it appears maybe casing is getting manipulated after preferredName is sent from the Profile page to vets-api.
Possible tasks:
Acceptance criteria
In case where a Veteran's data in VA.gov includes a first name but not a preferred name, the name capitalization in the landing page "Welcome" message matches the capitalization in the auth menu in the header.
Determined whether we have to do anything in vets-website or vets-api to preserve user's intended capitalization of preferredName, and ticketed if needed
QA review
The text was updated successfully, but these errors were encountered:
Description
User story
As a Veteran, I don't want my first name in the welcome message on the MHV landing page to be displayed in all caps, so that I feel as welcome as intended.
Notes
vets-api
.Possible tasks:
Acceptance criteria
vets-website
orvets-api
to preserve user's intended capitalization of preferredName, and ticketed if neededThe text was updated successfully, but these errors were encountered: