Closed julien-deramond closed 1 month ago
Do you agree that the values of a border style are limited to the four provided? A new style of border cannot be added without a modification of the library code so I suggest that we materialize String values like border style by an enum. In the code we will have a switch with an else case for not handled values.
A border radius should always have the same type, here we have a percentage for circle border radius where the other are integers. As Kotlin is typed, we have a problem with this.
After meeting: remove border-radius-circle
.
⚠️ On hold until https://github.com/ouds-sandbox/ouds-android/issues/34
Description
The aim of this issue is to study and implement the border tokens taking into account the cohesive multi-platform approach, the customization by libraries inheriting OUDS Android, but also what we're using for OUDS Android: Jetpack Compose, Material 3, etc.
Reminder: there will be in the end 3 layers of tokens:
Tokens: Border
Raw primitive values
Width
Radius
Style
Semantic applications
Width
Radius
Style
Study
Technical details
OudsCustomTheme
interface of the "theme-contract" module and specify the default value for each semantic coming from "tokens-global-raw" module⚠️ No need to override border semantic tokens in themes because default values are the Orange ones