Orange-OpenSource / Orange-OpenSource/ouds-android
In `library`, add `list item` component v0.2
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 22
- Forks
- 5
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 30
Description
Description
As a user of the OUDS library
I want to be able to use the component
So that I can add an OUDS component in my own projects
As a user of the library
I want to be able to use the component
So that I have access to the documentation on how to use it
As a user of the Design System Toolbox pp
I want to access the Component
So that I can understand how to use it:
- while using the design system toolbox app I can interact with the available options and observe the changes on the component itself
- I can see the code associated to the component customization
- I can copy and paste the code from the app based on the selected customization
- or when looking into the code of the app itself, I would also understand how to use it
Details
Verbatims from @MaximeTonnerre about prioritization of the component below.
Note that a component in version 0 must be seen as draft.
v0.2
- Text container: slots
- Leading: slot (see with Maxime for the size of the slot width/height)
- Trailing: slot (see with Maxime for the size of the slot width/height)
Specific use cases
- Let users add a custom view instead of image / icon in leading position but with sizes constrained to the 3 available
- Let users change the color of the texts (or maybe at least the text above)
Other notes
Here is an initial list of usage rules that we can already identify:
The management of the “Rounded corner” variant is the same as for the other affected components. It is not possible to have both renderings on the same product (except for the “Grouped + Divider” use case where the rounded corner is not applicable).
The “Size” variant must be applied to the entire list (the “Grouped” use case).
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
No source files, tests, or entry points are named. Start by reviewing the existing library components and the linked Figma reference, then trace how components are exposed in the Design System Toolbox. Done means the list item supports the specified text, leading, and trailing slots, documented customization, and interactive toolbox examples with copyable code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- design, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100