Orange-OpenSource / Orange-OpenSource/ouds-android

Common Cross-Libraries Token Architecture: Add Semantic Tokens From Outside

Open
#45 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

⚠️ on hold 🗳️ feature
Dominant language
Kotlin
Stars
22
Forks
5
Avg merge
3d 12h
Merged PRs (30d)
30

Description

[!WARNING]
On hold until the common cross-libraries token architecture has been implemented and challenged with the creation of some components

Description

The possibility of adding semantic tokens from outside was envisaged in https://github.com/Orange-OpenSource/ouds-android/issues/34, but it was not studied in depth at the time. The complexity of creating prototypes without an existing library made this task challenging. Strategically and efficiently, adding semantic tokens from outside was deemed out of scope.

Now that the common cross-library token architecture has been implemented and validated through the creation of various components, it's time to study and implement the second version of this architecture. This new version will allow the addition (and possibly removal) of semantic tokens from outside when creating a new theme.

Study
  • Study the limitations and the way it could be done on Android
Technical details

TODO

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing issue #34 and the common cross-library token architecture referenced in this issue. Study the limitations of adding semantic tokens from outside when creating an Android theme, including whether removal is feasible. Done means the approach is documented and the second architecture version is implemented and validated with components.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
design, mobile-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.