Inconsistent behaviour on remove last item (vs remove all items)

Are you asking a question?

No.

Are you reporting a bug or runtime error?

An error in your example, a runtime error, and a bug.

An error in your example in this page: https://react-select.com/creatable

Specifically Multi-select text input and the method handleKeyDown;

  handleKeyDown = (event: SyntheticKeyboardEvent<HTMLElement>) => {
    const { inputValue, value } = this.state;
    if (!inputValue) return;
    switch (event.key) {
      case 'Enter':
      case 'Tab':
		//... etc... 
        this.setState({
          inputValue: '',
          value: [...value, createOption(inputValue)],
        });
        event.preventDefault();
    }
  };

The line value: [...value, createOption(inputValue)], assumes …value is always an array; this is NOT true; value becomes null when you remove the last item, by clicking on the individual item;

Herein lies the bug: Inconsistent behaviour when removing the last item. When removing an individual last item (click on small-x), value = null; When removing all items (click on big-x), value = [];

Are you making a feature request?

No. it is a bug fix. Please make the behavior consistent on item removal, so that even your own example works.

[joe-oli]

Did you have any other questions or concerns regarding this approach

Thank you, no more questions now that it is clear what to expect.

[dakur]

@joe-oli I don’t know in which issue I have read it, but the answer – as I understood it – is null for now, but may be rethought to [] in future.

Ha, it’s here: https://github.com/JedWatson/react-select/issues/4293#issuecomment-759601523

• Clearing the value from isMulit Select will return the value null to be consistent with current implementation.
  • It should be noted that it was discussed that this approach for returning null for multi Select can be confusing and will likely be reverted back to [] in v4.0