Why was comma create new tag functionality removed?
See original GitHub issueSo there is this block of commented out code:
// case 188: // ,
// if (this.props.allowCreate && this.props.multi) {
// event.preventDefault();
// event.stopPropagation();
// this.selectFocusedOption();
// } else {
// return;
// }
// break;
and I was wondering why it is commented out? Being able to create a new tag on the comma key is a pretty big deal for me and was wondering when this would be added back in?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:26 (2 by maintainers)
Top Results From Across the Web
Topic: Removing commas in Tags | WordPress.com Forums
Commas are used to separate tags when you add them and are supposed to be stripped out – this is not a bug....
Read more >How can I remove commas when adding tags?
Commas aren't stored in the actual tag, they're injected when tags are rendered. Whatever your tag-removal solution will be, it'll happen ...
Read more >Remove commas from tags - GeneratePress
Hi,. when I use this code provided by Tom (only the part regarding the commas), the icon before the text is no longer...
Read more >Create a new record by value (split using comma) u...
A new record with value 'a' is created but another record with value ='b' is not created. and the existing cannot be deleted......
Read more >Remove "comma" between blog meta data tags
Note - would only like to remove commas of the meta item tag, not category ... Blog-meta-item--tags').map(function(val, i) { this.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
FYI I just pushed PR #1213 to add a little better guard around this.
FWIW I believe that’s b’c we’re now concatenating existing options before calling
this.isOptionUnique
.