Handling many tagsinput
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, react
- Domain
- frontend
Research direction
Start by reviewing the react-tagsinput component and its existing usage patterns for multiple instances in one form or component. The issue does not name a file, test, expected API, or acceptance criteria; clarify how many inputs should be supported and what "supported" means before choosing an implementation. Done should include a defined behavior and coverage for the requested usage.
Written by the indexing model from the issue text.
Description
How to handle many tagsinput in a form or in a same component. It seems, it isn't supported
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 229
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from olahol/react-tagsinput
-
prop-types is required at runtime but only listed in devDependenciesPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
olahol/react-tagsinput#229 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 60/100
olahol/react-tagsinput#199 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
olahol/react-tagsinput#223 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
olahol/react-tagsinput#222 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 38/100
olahol/react-tagsinput#217 · 1 comment ·
All issues in olahol/react-tagsinput
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
swc-project/swc-next#1022 ·
Maintainers usually reply within 1 day
-
area-clientside-dartpad
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
alphagov/public-asset-checker#378 · 1 comment ·
Maintainers usually reply within 1 day
-
headers-parser: `forRegExp` does not escape regexp characters in path segments that contain `*`Possibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day