Orange-OpenSource / Orange-OpenSource/Orange-Boosted-Bootstrap

Create component - Pin code input

Open
#3,137 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

⚛️ component 📖 documentation 🔍 triage 🧰 library
Dominant language
CSS
Stars
219
Forks
61
Avg merge
2d 15h
Merged PRs (30d)
12

Description

Description

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

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

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
  • Length
  • Error
  • Helper text (bool)
  • Helper text (4 digit code) (text)
  • Helper text (6 digit code) (text)
  • Helper text (8 digit code) (text)

Others

  • Implementement Initial settings
  • Update tests
  • Update documentation
  • Update demo

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 the component description in the Figma board and the linked Orange Unified Design System guidelines. Use the existing library, tests, documentation, and demo patterns as entry points, since no specific files are named. Done means the listed properties are supported, tests are updated, documentation explains usage, and the demo exposes customization and copyable code.

Written by the indexing model from the issue text.

Assessment

Tech stack
bootstrap, css
Domain
documentation, frontend, testing
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.