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

Epic: Validation on components #4598

Open
geospatialem opened this issue May 19, 2022 · 9 comments
Open

Epic: Validation on components #4598

geospatialem opened this issue May 19, 2022 · 9 comments
Assignees
Labels
1 - assigned Issues that are assigned to a sprint and a team member. design Issues that need design consultation prior to development. epic Large scale issues to be broken up into sub-issues and tracked via sprints and/or project. p - medium Issue is non core or affecting less that 60% of people using the library ready for dev Issues ready for development implementation.

Comments

@geospatialem
Copy link
Member

geospatialem commented May 19, 2022

Background

This epic organizes validation related issues in one place for the team to sift through the various tasks once the team is able to address validation around components.

Plan of action

Anticipated after v1.0.0 release

Issues

Once the above are completed, revisit:

@geospatialem geospatialem added the epic Large scale issues to be broken up into sub-issues and tracked via sprints and/or project. label May 19, 2022
@github-actions
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale Issues or pull requests that have not had recent activity. label Jun 19, 2022
@github-actions
Copy link
Contributor

This issue has been automatically closed due to inactivity.

@geospatialem
Copy link
Member Author

This issue has been automatically closed due to inactivity.

Reopening as this is still in progress.

@geospatialem geospatialem reopened this Jun 27, 2022
@benelan benelan removed the Stale Issues or pull requests that have not had recent activity. label Jun 27, 2022
@geospatialem geospatialem added the 0 - new New issues that need assignment. label Jul 19, 2022
@brittneytewks brittneytewks added design Issues that need design consultation prior to development. needs triage Planning workflow - pending design/dev review. labels Jun 1, 2023
@geospatialem geospatialem added this to the Design Sprint Next milestone Jun 1, 2023
@geospatialem geospatialem added p - medium Issue is non core or affecting less that 60% of people using the library and removed needs triage Planning workflow - pending design/dev review. labels Jun 1, 2023
@ashetland
Copy link

Including issues #5079 and #2793 into this effort. We’ve been discussing incorporating Label and Input Message into form components while continuing to maintain the separate Label and Input message components for the time being. This would allow us to add requested functionality to Label and improve standardization on layout and behaviors while also preserving the ability to customize. cc @jcfranco

@SkyeSeitz
Copy link

Figma file documenting audit details can be found here

@SkyeSeitz
Copy link

Audit reviewed by Brittney & Franco. Ready to create remaining issues and triage in our next sync @geospatialem

@geospatialem
Copy link
Member Author

Once #9229 is verified with this codepen, the remaining issues should be confirmed as working with the pattern of validity, status and (optionally) required from #8057 (comment).

If all issues are mitigated with the above pattern ⬆️ , we can close the above in addition to:

cc @DitwanP

@geospatialem geospatialem added 3 - installed Issues that have been merged to master branch and are ready for final confirmation. and removed 1 - assigned Issues that are assigned to a sprint and a team member. labels Apr 30, 2024
Copy link
Contributor

Installed and assigned for verification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - assigned Issues that are assigned to a sprint and a team member. design Issues that need design consultation prior to development. epic Large scale issues to be broken up into sub-issues and tracked via sprints and/or project. p - medium Issue is non core or affecting less that 60% of people using the library ready for dev Issues ready for development implementation.
Projects
None yet
Development

No branches or pull requests

7 participants