Orange-OpenSource / Orange-OpenSource/ouds-android

[Component] Create component - Select input (v1.3.1)

Open
#807 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

⚛️ component 📖 documentation 📱 demo app 🧰 library
Dominant language
Kotlin
Stars
22
Forks
5
Avg merge
3d 12h
Merged PRs (30d)
30

Description

Description

As a user of the library
I want to be able to use the component select input
So that I can add configurable select input 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
I want to access the component
So that I can understand how to use it:

  • while using the demo 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

About v1.3.1

Verbatims from @TonyAntonyHello:

For “Loading" state
- The loader frame has been renamed to Circular progress indicator
- The following token has been removed: action-button-border-radius-default
- Absolute positioning has been removed and replaced with Auto Layout.
- The container now uses: ouds/action/button/space/inset/icon-only-default

About v1.3

Verbatims from @MaximeTonnerre:

Release note:

- Scope: Trailing action=False / State=Loading → Replacement of the button component (loading state) with a “Trailing container” frame containing the circular progress indicator component
- The input text reference changes from a regular weight (font-weight-label-default) to a medium weight (font-weight-label-moderate).
- Removal of the component’s max-width to avoid blocking certain layouts and to provide greater flexibility of use. The max-width values remain available in the design documentation.
- Update of the tokens applied to the chevron. Depending on the component’s state, the tokens applied to the chevrons are replaced by a component token from the button family (example: color-content-default → action-button-color-content-enabled).

See Figma specifications

Design guidelines

unified-design-system.orange.com

Context

The component is described in the Figma board, and is available in version v1.2.0

Definition of Ready

To be defined

Definition of Done

Properties to manage

  • Outlined
  • Rounded corner
  • Input status
  • State
  • Error
  • Leading icon
  • Label (bool)
  • Label (text)
  • Input text
  • Combobox
  • Autocompletion (bool)
  • Autocompletion (text)
  • Helper text (bool)
  • Helper text (text)
  • Error empty text
  • Error filled text
  • Helper link

Others

  • Implementement Initial settings
  • Update tests
  • Update documentation
  • Update design system toolbox app

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 with the linked Figma specifications and review how the existing v1.2.0 select input is represented in the Android library. Check the component tests, documentation, and Design System Toolbox app entry points before implementing the listed properties and settings. Done means the tests, documentation, and demo app are updated for the v1.3.1 behavior.

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
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.