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

Form Caption Group - Ensure Consistency between Storybook Documentation and Codebase Property Names #878

Closed
2 of 6 tasks
angelicahoyss opened this issue Feb 4, 2024 · 0 comments · Fixed by #981
Closed
2 of 6 tasks
Assignees
Labels
⭕ core team issue This is for the core team and should not be done by contributors ⌨️ dev issue Task is for developers 🎓 junior issue Good for juniors

Comments

@angelicahoyss
Copy link
Contributor

angelicahoyss commented Feb 4, 2024

Description / User story

As a developer on the team,
I want to ensure consistency between the property names defined in the Storybook documentation for Form Caption Group component
So that the Form Caption Group component codebase accurately reflects the documented property names.

This user story outlines the need to maintain consistency between the documentation and the codebase regarding component property names. Each component is checked to ensure the property names in the codebase match the corresponding names in the Storybook documentation. If the discrepancies are found, they are listed in this table on the page "FormCaptionGroup". Column Current Code Property Name describes how is the property currently named in the code. Column Desired Code Property Name is how the property should be named. Properties marked green don't need adjustment.

Acceptance Criteria

  • All Form Caption Group component's property names that differ from Storybook documentation property names (listed in the above mentioned table) should be updated
  • 'size' property should be renamed to 'sizeVariant' in Storybook documentation
  • The updated property names should not introduce any unintended side effects or issues in the functionality of the components
  • The library builds successfully, and there are no reported issues related to the property name updates
  • Props Excel has been updated / comments have been resolved and props changed from red to black font color > @thrbnhrtmnn or @angelicahoyss can support here

Code of Conduct

  • I agree to follow this project's Code of Conduct
@angelicahoyss angelicahoyss added ⌨️ dev issue Task is for developers ⭕ core team issue This is for the core team and should not be done by contributors 🎓 junior issue Good for juniors labels Feb 4, 2024
@angelicahoyss angelicahoyss added this to the Prop alignment milestone Feb 4, 2024
@JpunktWpunkt JpunktWpunkt self-assigned this Mar 5, 2024
@JpunktWpunkt JpunktWpunkt linked a pull request Mar 5, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⭕ core team issue This is for the core team and should not be done by contributors ⌨️ dev issue Task is for developers 🎓 junior issue Good for juniors
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants