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

Front end: Modify VAMC System template to opt out of USWDS V3 automatic upgrade #17034

Closed
1 task
xiongjaneg opened this issue Jan 25, 2024 · 3 comments
Closed
1 task
Assignees
Labels
Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status sitewide VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team

Comments

@xiongjaneg
Copy link
Contributor

xiongjaneg commented Jan 25, 2024

User Story or Problem Statement

On 2/16, USWDS V1 components will default to V3. V1 components that have V3 versions will be automatically upgraded unless we opt out proactively. Opting out means: modifying those existing V1 components to pass in the uswds={false}.

VAMC System templates needs to be modified to opt out of V1 to V3 automatic upgrade.

v3 components

Acceptance Criteria

  • Existing V1 components that have a v3 equivalent are modified to pass in the uswds={false}
@xiongjaneg xiongjaneg added Needs refining Issue status Facilities Facilities products (VAMC, Vet Center, etc) VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team labels Jan 25, 2024
@xiongjaneg
Copy link
Contributor Author

Hey team! Please add your planning poker estimate with Zenhub @eselkin @maxx1128

@eselkin
Copy link
Contributor

eselkin commented Jan 25, 2024

I pointed as a 3. The reason so high is it's going to require building and rebuilding content-build many times.

@xiongjaneg
Copy link
Contributor Author

Closing, not currently using V1 components with V3 equivalents

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status sitewide VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team
Projects
None yet
Development

No branches or pull requests

4 participants