Address component

[jimmoffet]

Overview

Form builder user can easily create (or convert an existing generic fieldset) an address component with sensible defaults.

Context

Optional: Any reference material or thoughts we may need for later reference, or assumptions of prior or future work that's out of scope for this story.

• [ ]

Acceptance Criteria

Required outcomes of the story

• [ ] Form-builder UI works as expected by form builder users, display show the expected component, no surprises
• [ ] Abides USWDS best practice guidelines as defined on component page (ala https://designsystem.digital.gov/patterns/create-a-user-profile/address/)
• [ ]

Research Questions

• Optional: Any initial questions for research

Tasks

Research, design, and engineering work needed to complete the story.

• [ ]

Definition of done

The "definition of done" ensures our quality standards are met with each bit of user-facing behavior we add. Everything that can be done incrementally should be done incrementally, while the context and details are fresh. If it’s inefficient or “hard” to do so, the team should figure out why and add OPEX/DEVEX backlog items to make it easier and more efficient.

• [ ] Behavior
  • [ ] Acceptance criteria met
  • [ ] Implementation matches design decisions
• [ ] Documentation
  • [ ] ADRs (/documents/adr folder)
  • [ ] Relevant README.md(s)
• [ ] Code quality
  • [ ] Code refactored for clarity and no design/technical debt
  • [ ] Adhere to separation of concerns; code is not tightly coupled, especially to 3rd party dependencies; dependency rule followed
  • [ ] Code is reviewed by team member
  • [ ] Code quality checks passed
• [ ] Security and privacy
  • [ ] Automated security and privacy gates passed
• [ ] Testing tasks completed
  • [ ] Automated tests pass
  • [ ] Unit test coverage of our code >= 90%
• [ ] Build and deploy
  • [ ] Build process updated
  • [ ] API(s) are versioned
  • [ ] Feature toggles created and/or deleted. Document the feature toggle
  • [ ] Source code is merged to the main branch

Decisions

• Optional: Any decisions we've made while working on this story

[JennyRichards-Flexion]

Dependent on #360 completion.

With something like Select, is there a template of data we can pre-load into Select (like a list of 50 states)? Jim thinks this is handled by the US WDS Address template. We should be able to import this wholesale. Dan says we can hard code it based on guidance.

[JennyRichards-Flexion]

Includes basic validation for standard address without any complexity added. This item is largely implemented - but it might have been disabled. There is validation in there for state/territories already.

Review what's there and relate it back with the AC. Testing also needed.