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

[MHV-55186] Update all V1 components to V3 web components on SM MHV #28504

Closed
wants to merge 42 commits into from

Conversation

vsaleem
Copy link
Contributor

@vsaleem vsaleem commented Mar 12, 2024

Summary

  • V1 Web-Components are retired. This update switches all va-components to utilize the V3 uswds web-components.

Explanation:
The components are currently built so one can flip between v1 and v3. But that bloats the components with code that isn't being used. Once v1 is deprecated we'll commence removing that code.

Also, for the sake of consistency we want to move va.gov to v3 components within a reasonable time frame. Thus hanging on to v1 versions makes that process take longer. @humancompanion-usds

Related issue(s)

[MHV-55186] Update Retired V1 components to V3

Testing done

  • Manual Testing

To test, start on the 'Messages' landing page and click through all elemental components, (i.g. Accordion, Alerts, Links, etc.), and use google DOM to check if each component contains "uswds" attribute.

Screenshots

Note: This field is mandatory for UI changes (non-component work should NOT have screenshots).

Before After
Mobile
Desktop

What areas of the site does it impact?

(Va.gov - Secure Messaging)

Acceptance criteria

AC1 All components have been upgraded to V3

AC2 V3 Components to test:

  • Va-Accordion
  • Va-Additional-Info
  • Va-Alert
  • Va-Button
  • Va-Modal
  • Va-Pagination
  • Va-Radio
  • Va-Select
  • Va-Text-Input
  • Va-Textarea

Quality Assurance & Testing

  • I fixed|updated|added unit tests and integration tests for each feature (if applicable).
  • No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
  • Linting warnings have been addressed
  • Documentation has been updated (link to documentation *if necessary)
  • Screenshot of the developed feature is added
  • Accessibility testing has been performed

Error Handling

  • Browser console contains no warnings or errors.
  • Events are being sent to the appropriate logging solution
  • Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

  • Did you login to a local build and verify all authenticated routes work as expected with a test user

⚠️ Team Sites (only applies to modifications made to the VA.gov header) ⚠️

  • The vets-website header does not contain any web-components
  • I used the proxy-rewrite steps to test the injected header scenario
  • I reached out in the #sitewide-public-websites Slack channel for questions

Requested Feedback

(OPTIONAL) What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?

@va-vfs-bot va-vfs-bot temporarily deployed to master/55186-Update-all-V1-components-to-V6-on-sm-mhv/main March 12, 2024 17:08 Inactive
Copy link
Contributor

@oleksii-morgun oleksii-morgun left a comment

Choose a reason for hiding this comment

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

Awesome 😃 Just one minor comment to get clarification on heading

className="vads-u-margin-bottom--0 vads-u-font-size--base vads-font-family-sans-serif"
>
File attached
</h3>
Copy link
Contributor

Choose a reason for hiding this comment

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

Was this h3 suggested by a11y? trying to see the rationale behind replacing p with heading tag

@va-vfs-bot va-vfs-bot temporarily deployed to master/55186-Update-all-V1-components-to-V6-on-sm-mhv/main March 12, 2024 21:06 Inactive
@va-vfs-bot va-vfs-bot temporarily deployed to master/55186-Update-all-V1-components-to-V6-on-sm-mhv/main March 12, 2024 23:45 Inactive
@va-vfs-bot va-vfs-bot temporarily deployed to master/55186-Update-all-V1-components-to-V6-on-sm-mhv/main March 13, 2024 18:41 Inactive
@va-vfs-bot va-vfs-bot temporarily deployed to master/55186-Update-all-V1-components-to-V6-on-sm-mhv/main March 13, 2024 23:27 Inactive
@va-vfs-bot va-vfs-bot temporarily deployed to master/55186-Update-all-V1-components-to-V6-on-sm-mhv/main March 15, 2024 16:53 Inactive
@va-vfs-bot va-vfs-bot temporarily deployed to master/55186-Update-all-V1-components-to-V6-on-sm-mhv/main March 15, 2024 19:35 Inactive
@va-vfs-bot va-vfs-bot temporarily deployed to master/55186-Update-all-V1-components-to-V6-on-sm-mhv/main March 15, 2024 19:58 Inactive
Copy link
Contributor

@micahchiang micahchiang left a comment

Choose a reason for hiding this comment

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

With the merge of this PR on Friday, you should no longer need to include the uswds prop in any of your web component declarations.

@va-vfs-bot va-vfs-bot temporarily deployed to master/55186-Update-all-V1-components-to-V6-on-sm-mhv/main March 18, 2024 17:21 Inactive
@oleksii-morgun
Copy link
Contributor

@vsaleem per #28504 (review) as we chatted on Friday, at this point we would only need uswds=false where we need to keep V1 until we work on fixes

@va-vfs-bot va-vfs-bot requested a review from a team March 18, 2024 21:09
Copy link

@va-vfs-bot va-vfs-bot left a comment

Choose a reason for hiding this comment

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

Icon found

Icons can be decorative, but sometimes they are used to convey meaning. If there are any semantics associated with an icon, those semantics should also be conveyed to a screen reader.

What you can do

Review the markup and see if the icon provides information that isn't represented textually, or wait for a VSP review.

))}
{activeFolder.folderId !== DefaultFolders.DRAFTS.id && unreadMessages && (
<span>
<i

Choose a reason for hiding this comment

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

icon found

))}
{activeFolder.folderId !== DefaultFolders.DRAFTS.id && unreadMessages && (
<span>
<i

Choose a reason for hiding this comment

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

icon found

@va-vfs-bot va-vfs-bot temporarily deployed to master/55186-Update-all-V1-components-to-V6-on-sm-mhv/main March 18, 2024 21:10 Inactive
@va-vfs-bot va-vfs-bot temporarily deployed to master/55186-Update-all-V1-components-to-V6-on-sm-mhv/main March 18, 2024 21:29 Inactive
@va-vfs-bot va-vfs-bot temporarily deployed to master/55186-Update-all-V1-components-to-V6-on-sm-mhv/main March 18, 2024 21:34 Inactive
@va-vfs-bot va-vfs-bot temporarily deployed to master/55186-Update-all-V1-components-to-V6-on-sm-mhv/main March 18, 2024 21:47 Inactive
@vsaleem
Copy link
Contributor Author

vsaleem commented Apr 10, 2024

Closing this pull request as it is no longer needed. These issues are being handled in individual stories. V3 Component-Issues resulting from upgrade

@vsaleem vsaleem closed this Apr 10, 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.

None yet

5 participants