shift+enter not working and check event
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, react
- Domain
- frontend
Research direction
Start by reproducing the Shift+Enter behavior and the onChange interaction shown in the TagsInput example. Inspect the component's input and event handling, then verify that Shift+Enter creates a new line and that the relevant event values are accessible.
Written by the indexing model from the issue text.
Description
Hi,
when i press shift+enter not going to new line and also how to check event values in
unable to access event values
- 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 @Tanishdete333 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
olahol/react-tagsinput#229 · 2 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 60/100
olahol/react-tagsinput#199 ·
-
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 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
olahol/react-tagsinput#216 ·
All issues in olahol/react-tagsinput
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
module-federation/core#5205 ·
Maintainers usually reply within 1 day
-
affects:v0.5.2 area:frontend audit:ui-ux-2026-10 bug priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
berntpopp/kidney-genetics-db#326 ·
Maintainers usually reply within 1 day
-
task
Difficulty 1/5 Under an hour Newbie friendliness 83/100
TAMULib/fw-registry#550 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
-
NWCWalletService.subscribe: response is never published if the handler finishes after unsubscribe (regression in 8.1.0)Possibly taken @ajaysehwal claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100