You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As Software Engineer
I want to have a consistent way of naming parameters
So that the user of the Design System can easier navigate our components
Description
We have inconsistent approach to naming parameters.
When dealing with a component that has a some text and a href (nav, service nav, language etc) we don't use the same name conventions. Navigation uses title and path and service navigation uses text and url.
We need to review and update so we use consistent parameters names.
For Access Code we currently have
postTextboxLinkText
postTextboxLinkUrl
Acceptance Criteria
Naming convention to this component has been agreed within Dev team.
Naming convention has been applied to the component.
Visualisation/Input from UCD
How should the components look like?
As Software Engineer
I want to have a consistent way of naming parameters
So that the user of the Design System can easier navigate our components
Description
We have inconsistent approach to naming parameters.
When dealing with a component that has a some text and a href (nav, service nav, language etc) we don't use the same name conventions. Navigation uses title and path and service navigation uses text and url.
We need to review and update so we use consistent parameters names.
For Access Code we currently have
Acceptance Criteria
Visualisation/Input from UCD
How should the components look like?
Linked User stories/epics
Outcome of the spike
Technical details (optional)
MVP (optional)
The text was updated successfully, but these errors were encountered: