Febakke
commented
3 weeks ago Cleaner settings
- Move label and description out of subcomponent and have them as elements of the master component.
- Size will be removed making it easier to add sub-components to settings
- Add more text properties
- States need to be the same on all "similar" components
Keep overrides across component swapping
Case: I want to swap between form components and keep all my overrides. Solution: If we want to support this all elements needs to have the same names as overrides are mostly handled by naming.
Test:
Kept: Label and description
Not overridden: Input text and state (error message)
Also testet radio/check. Overrides only handled for legend/description
Label and description: Works as is Text inside fields: Maybe we can support this if we give fields generic names Error-message: Should work as is radio/check labels and descriptions: If we want overrides to work across these components the "list" elements need to have the same name inside both components. I suggest we do this so users can swap between radio and check and keep labels and descriptions
We have gotten feedback that users want to edit text in the component properties. For this to work without showing all settings for core components we need to swap typography components with text styles. This is a major breaking change, so we need to careful so that we dont overwrite all text used in apps.
We will keep typography components as they contain the correct use of color tokens.