-
Notifications
You must be signed in to change notification settings - Fork 0
35 ‐ Rules about tokens, themes, components and modules
Pierre-Yves Lapersonne edited this page Apr 18, 2025
·
4 revisions
- Raw tokens are frozen and cannot be changed
- Raw tokens can be shared between themes
- Raw tokens can be exclusive to some themes
- Raw tokens can be generated by the tokenator
- Raw tokens can be defined without tokenator
- Raw tokens are defined with raw and primitive values
- Semantic tokens can be overriden by themes
- Semantic tokens can not be overridable by themes, i.e. frozen values
- Semantic tokens can be shared between themes
- Semantic tokens can be generated by the tokenator
- Semantic tokens can be defined without tokenator
- Semantic tokens can not be created (but technicaly possible if context outside OUDS Swift Package)
- Semantic tokens can be defined with raw tokens
- Semantic tokens can be defined with semantic tokens
- Semantic tokens of colors for repository group must not be overridable
- Component tokens can be overriden by themes
- Component tokens can be shared between themes
- Component tokens can be generated by the tokenator
- Component tokens can be defined without tokenator
- Component tokens can not be created (but technicaly possible if context outside OUDS Swift Package)
- Component tokens can be defined with raw tokens
- Component tokens can be defined with semantic tokens
- A theme does not need to create its raw tokens to exist
- A theme can define its raw tokens and use them
- A theme can override some semantic tokens with shared raw tokens
- A theme can override some semantic tokens with exclusive / internal raw tokens
- A theme can override some semantic tokens with semantic tokens
- A theme can be overridable to make subtheme
- A theme can be not overridable to prevent to have subthemes
- A theme can be defined outside OUDS Swift Package, open source or not
- The demo application must reflect what the library provides without additional features (except legals)