JedWatson / JedWatson/react-select

Creatable component is not editable + bad UX

Open
#4,982 4 comments 35 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

issue/bug-unconfirmed
Dominant language
TypeScript
Stars
28k
Forks
4.1k
PR merge metrics
No merged PRs in 30d

Description

I'd like to apologize in advance for not using the "Discussions" feature and instead filling a bug report.

That said, I'd really like to know where is this project going in regards with it's "editability". There are multiple bug reports[1][2][3][4][5][6] as well as discussions [7] (which, btw, is the most voted discussion by far) requesting basically the same feature: a real editable behavior.

There's the CreatableSelect component which allows for custom values to be inserted, but once inserted they can't be edited in any way. The only way to actually "edit" the inserted value is to delete it and type it again (really bad UX, especially infuriating if a really long value was inserted and there is a typo).

Then there is the isMulti prop, which allows for multiple values to be selected and/or created. But the same problem happens if/when one of the values must the edited.

Some users even tried to implement "editable tags"[8] (I'm guessing so that they could, somehow, inject that component inside react-select ¿?).

None of this bugs / discussions ended up being fixed / implemented, yet a lot of people seem to be interested in such a functionality. More important, this interest doesn't seem to vanish across the years (oldest bug report I could find related to this problem is from 2016).

Please do note that I'm not trying to demand or impose anything at all. You guys (the maintainers of this project) are doing excellent job and I'm so much thankful for your effort on this. I'd just like to know if there are plans for implementing this (and if "yes" what would help you to do it) or if this is something that is not in your current priorities.

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 CreatableSelect and isMulti behaviors described in this issue, then compare the linked reports and discussion for existing requirements. Done would require an agreed editable-value design and an implementation plan; this report names no files or tests, so it is not independently startable.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.