Set the uswds prop's default value to true for all compoents with a v…

[it-harrison]

…3 version

Chromatic

https://2405-usdws-default-true--60f9b557105290003b387cd5.chromatic.com

---

Configuring this pull request

Description

This PR sets the default value for the uswds prop to true for all components with a v3 variant. It also makes adjustments to components that used composition with other components so that the correct version is used. Finally, it updates stories and moves up v3 stories to the top of the sidebar in Storybook.

Closes 2405

QA Checklist

• Component maintains 1:1 parity with design mocks
• Text is consistent with what's been provided in the mocks
• Component behaves as expected across breakpoints
• Accessibility expert has signed off on code changes (if applicable. If not applicable provide reason why)
• Designer has signed off on changes (if applicable. If not applicable provide reason why)
• Tab order and focus state work as expected
• Changes have been tested against screen readers (if applicable. If not applicable provide reason why)
• New components are covered by e2e tests; updates to existing components are covered by existing test suite
• Changes have been tested in vets-website using Verdaccio (if applicable. If not applicable provide reason why)

Screenshots

Acceptance criteria

• QA checklist has been completed
• Screenshots have been attached that cover desktop and mobile screens

Definition of done

• Documentation has been updated, if applicable
• A link has been provided to the originating GitHub issue (or connected to it via ZenHub)

[powellkerry]

Should we rename the USWDS section in storybook to "Components" and change the section for the v1 components to something else?

[micahchiang]

@it-harrison - Should this PR include a version bump to the web components package? Or, would you prefer to do that in a separate PR when we bump core for the release of this stuff?

[jamigibbs]

In the Chromatic link, I think some USWDS components might have been missed to move them into the top "Components" section:

[it-harrison]

In the Chromatic link, I think some USWDS components might have been missed to move them into the top "Components" section:

@jamigibbs thanks - fixed

[jamigibbs]

ope! Just noticed a few stragglers. The v1 version of va-alert and va-textarea and va-text-input are hanging out next to the v3 versions. Should they be moved down to the V1 Components section too?

[ataker]

We may need an exception here. v3 va-process-list expects va-process-list-item as its children while v1 expects li. This will break v1s being auto-upgraded to v3

[micahchiang]

Good call out here @ataker. I think what we'll do is go with @jamigibbs's suggestion to set all of the necessary instances in vets-website to uswds=false. There aren't that many, and it unblocks our release plans for next week.