Skip to content

LG-14049 Fix barcode info alert dates and content#11398

Merged
shanechesnutt-ft merged 1 commit intomainfrom
sc/LG-14049
Nov 7, 2024
Merged

LG-14049 Fix barcode info alert dates and content#11398
shanechesnutt-ft merged 1 commit intomainfrom
sc/LG-14049

Conversation

@shanechesnutt-ft
Copy link
Contributor

@shanechesnutt-ft shanechesnutt-ft commented Oct 25, 2024

changelog: User-Facing Improvements, In-person proofing, Fix barcode page due date format for Spanish, French, and Chinese translations; Improve Spanish translation for information alert.

🎫 Ticket

Link to the relevant ticket:
LG-14049

🛠 Summary of changes

Fixed barcode page due date format for Spanish (<day> de <month> de <year>), French (<day> <month> <year>), and Chinese (<year>年<month>]月<day>日) translations; Improved the Spanish translation for the information alert.

Note: This PR fixes the time.formats.event_date translation and will update other areas of the code found in the Other Areas of the screenshots section.

📜 Testing Plan

Provide a checklist of steps to confirm the changes.

  • Login through the oidc sinatra application selecting a non Enhanced In-person Proofing level of service.
  • Use an exisiting account or create an account
  • Continue through the In-person flow until reaching the barcode page
  • Ensure English, Spanish, French, and Chinese date formats are matching Jira Ticket AC
  • Ensure the Spanish translation for the the information alert matches the Jira Ticket AC

👀 Screenshots

EIPP Ready to Verify Page eipp_ready_to_verify_en eipp_ready_to_verify_es eipp_ready_to_verify_fr Screenshot 2024-11-05 at 5 01 14 PM
EIPP Ready to Verify Email eipp_ready_to_verify_email_en eipp_ready_to_verify_email_es eipp_ready_to_verify_email_fr eipp_ready_to_verify_email_zh
EIPP Ready to Verify Reminder Email eipp_ready_to_verify_reminder_email_en eipp_ready_to_verify_reminder_email_es eipp_ready_to_verify_reminder_email_fr eipp_ready_to_verify_reminder_email_zh
ID-IPP Ready to Verify Page ipp_ready_to_verify_en ipp_ready_to_verify_es ipp_ready_to_verify_fr ipp_ready_to_verify_zh
ID-IPP Ready to Verify Email ipp_ready_to_verify_email_en ipp_ready_to_verify_email_es ipp_ready_to_verify_email_fr ipp_ready_to_verify_email_zh
ID-IPP Ready to Verify Reminder Email ipp_ready_to_verify_reminder_email_en ipp_ready_to_verify_reminder_email_es ipp_ready_to_verify_reminder_email_fr ipp_ready_to_verify_reminder_email_zh

Other Areas

Account View - pending enrollment account_view_pending_en account_view_pending_es account_view_pending_fr account_view_pending_zh
Account View - date personal key was created account_view_personal_key_en account_view_personal_key_es account_view_personal_key_fr account_view_personal_key_zh
LG99 Screen lg99_screen_en lg99_screen_es lg99_screen_fr lg99_screen_zh
Verified Info Failure - Email verified_info_failure_email_en verified_info_failure_email_es verified_info_failure_email_fr verified_info_failure_email_zh
Verified Info Successfully - Email verified_info_successfully_email_en verified_info_successfully_email_es verified_info_successfully_email_fr verified_info_successfully_email_zh
Verify by mail - enter your verification code verify_by_mail_en verify_by_mail_es verify_by_mail_fr verify_by_mail_zh
Verify by mail - reminder email verify_by_mail_reminder_email_en verify_by_mail_reminder_email_es verify_by_mail_reminder_email_fr verify_by_mail_reminder_email_zh
Verify your information screen verify_info_en verify_info_es verify_info_fr verify_info_zh

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we use this for event date if the current one is wrong?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, I wasn't sure if the change should app wide or not which is why I created a new translation.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's worth considering. If the new translation is more correct and we're still using the old one in other places, we should probably lean towards updating the existing one unless there's a compelling reason not to.

Copy link
Contributor

@mitchellhenke mitchellhenke Oct 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have time.formats.full_date, time.formats.event_date, date.formats.long, which are all kind of similar to each other and time.formats.standard_long.

There are also other dates for IPP that use event_date, ex:

def formatted_ipp_due_date
I18n.l(user.pending_in_person_enrollment.due_date, format: :event_date)
end
so I think it's probably worth just updating event_date for this

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree I will update the time.format.event_date, but let me confirm with design to see if there is a compelling reason to not to update the format app wide.

@shanechesnutt-ft shanechesnutt-ft requested review from a team, jennyverdeyen and rutvigupta-design and removed request for a team October 25, 2024 15:21
Copy link

@rutvigupta-design rutvigupta-design left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@shanechesnutt-ft thanks for all the screenshots, this LGTM! Can you please tag me or Kelli once this is merged, so we can send screenshots back to the State Dept? Thank you!

Copy link
Contributor

@eileen-nava eileen-nava left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved! I didn't manually test this, however, I'm comfortable approving it based on the automated tests and screenshots. Thanks for doing this.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👏🏻

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is super readable. 👍🏻

Copy link
Contributor

@mitchellhenke mitchellhenke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should confirm whether we want to create a new format or update the existing one. I lean towards updating the existing one.

@shanechesnutt-ft
Copy link
Contributor Author

I think we should confirm whether we want to create a new format or update the existing one. I lean towards updating the existing one.

I updated the existing time.formats.event_date translations

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorta curious why this had to change from strftime to I18n.l, or was that more of a readability improvement / consistent change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That previous version wasn't displaying the months with the correct translated month name. The I18n.l or localize method will correctly translate the month names when formatting the date.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see the example follows what's in the ticket, but without any demarcations, how is someone supposed to differentiate dates like “2024112” between being January 12th or November 2nd?

Copy link
Contributor Author

@shanechesnutt-ft shanechesnutt-ft Nov 5, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Chinese Translation has been updated to be <year>年<month>月<day>日

e.g. January 12, 2024 would be 2024年1月12日

Copy link
Contributor

@jennyverdeyen jennyverdeyen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! I tested the ready to verify page as well as the emails and all the content updates appear correct to me. Thanks for the screenshots of all the other areas!

Copy link
Contributor

@eileen-nava eileen-nava left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did a second review. Good test coverage. Approved. (Caveat: I didn't manually test. I am comfortable approving this PR without manual testing, based on the automated tests.)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👏🏻

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good test coverage. 👍🏻

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏻

@rutvigupta-design
Copy link

@shanechesnutt-ft the updated Chinese date format LGTM! I'll send to DOS for LQA as well :)

changelog: User-Facing Improvements, In-person proofing, Fix barcode page due date format for spanish, french, and chinese translations; Improve spanish translation for information alert.

This commit updates the time.formats.event_date for Spanish, French, and
Chinese, so more than just EIPP/ID-IPP flows are affected by this
change. See #11398 for the areas
affected.
@shanechesnutt-ft shanechesnutt-ft merged commit b0a739c into main Nov 7, 2024
@shanechesnutt-ft shanechesnutt-ft deleted the sc/LG-14049 branch November 7, 2024 22:13
@aduth aduth mentioned this pull request Nov 12, 2024
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.

6 participants