Orange-OpenSource / Orange-OpenSource/ouds-android
Use `components` instead of `componentsTokens` in OUDS components
Open
Nobody has claimed this yet.
🛠️ technical
🧰 library
- Dominant language
- Kotlin
- Stars
- 22
- Forks
- 5
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 30
Description
Should we use components instead of componentsTokens in OUDS components then set componentsTokens private?
Originally posted by @paulinea in https://github.com/Orange-OpenSource/ouds-android/pull/1360#discussion_r3413383214
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the discussion in pull request 1360 and trace the current OUDS component uses of componentsTokens. Determine whether the public name should become components while componentsTokens becomes private; done when the naming decision is applied consistently without breaking existing component usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100