Radio - Ensure Consistency between Storybook Documentation and Codebase Property Names

[angelicahoyss]

Prerequisite

#824 is done and closed
#521 is done and closed

Description / User Story

As a developer on the team,
I want to ensure consistency between the property names defined in the Storybook documentation for Radio component
So that the Radio 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 "Radio". 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 Radio component's property names that differ from Storybook documentation property names (listed in the above mentioned table) should be updated
• The updated property names should not introduce any unintended side effects or issues in the functionality of the components
• "araiaLabel" should be renamed to ariaLabel in Storybook file (Documentation)
• 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

[thrbnhrtmnn]

Hey @angelicahoyss , I think you copy pasted the description from the checkbox issue, right? Checkbox was mentioned a few times in the user story in the description. I changed it now to "Radio".

[angelicahoyss]

Sorry @thrbnhrtmnn I thought I replaced it! Thank you :)

[bar-tay]

@thrbnhrtmnn I don't think the value prop is needed since we already use the label prop to manipulate the text

[thrbnhrtmnn]

Hey @bar-tay , you can ignore the value prop for now, as it has its own ticket: #824 .

We should discuss in a refinement session, if this change is really needed.

[bar-tay]

Hey @bar-tay , you can ignore the value prop for now, as it has its own ticket: #824 .

We should discuss in a refinement session, if this change is really needed.

Did we decide on what to do about the value prop?

[thrbnhrtmnn]

@bar-tay , no, not yet. But should still be able to do this ticket, just ignore the value prop for now. Last time i checked the PR it already looked good, but I was waiting for a dev to also have a look and approve before I would look again and approve