question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

1.0.0-rc.3 not working?

See original GitHub issue

Hello, didnt look too much into it, but i switched to 1.0.0-rc.3 and the multiselect didnt work for me. I upgraded from 1.0.0-rc.2. Multi select loadOptions didnt reload correctly when selecting/de-selecting. Didnt know if anyone had similar issues, figured I would report it! I downgraded back to 1.0.0-rc.2 and everything worked fine. Thanks for the library and contributions ❤️

<Select.Async
  name="tags"
  cache={false}
  clearable={false}
  multi={true}
  onChange={this.reactSelectChange.bind(this, "tags")}
  loadOptions={this.tagOptions.bind(this)}
  value={this.state.tags}
/>

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Reactions:9
  • Comments:14 (1 by maintainers)

github_iconTop GitHub Comments

9reactions
iadunn13commented, Mar 6, 2017

I’ve found what causes this to happen. In https://github.com/JedWatson/react-select/commit/732ba55866d4b3bafbefa40c20923cba70804a70 a modification was added to the render definition in lib/Async.js that will clear out the multi-Select’s options whenever you select a value. See lib/Async.js line 241

239    onChange: function onChange(newValues) {
240        if (_this3.props.multi && _this3.props.value && newValues.length > _this3.props.value.length) {
241            _this3.clearOptions();
242        }
243        _this3.props.onChange(newValues);
244    }

Commenting out the call to _this3.clearOptions will fix the issue, and I can’t think a reason why the options are even being cleared out here in the first place. Hopefully we can get some input from @JedWatson on what should be happening here so we can get it fixed.

4reactions
Fritcommented, Jun 9, 2017

+1 @dmk23, today found the same issue with clearOptions. This behaviour confuses many devs. ps: have no time, extended Async,

class Async extends Select.Async {
    clearOptions = () => {
        if (!this.props.clearAsyncOptions) {
            return;
        }
        this.setState({ options: [] });
    }
}
Read more comments on GitHub >

github_iconTop Results From Across the Web

Unable to install 1.0.0-rc.3 with NPM 7 · Issue #1993 - GitHub
Bug report Describe the bug I'm playing around with the new npm 7 beta and received some errors installing Chakra.
Read more >
ESLint 1.0.0-rc-3 released - ESLint中文文档
We just pushed ESLint 1.0.0-rc-3, which is the third release candidate for 1.0.0. ... Moving the tester into the eslint module fixed a...
Read more >
Automatic refresh on collection-repeat stopped working on ...
Now go to the options tab and click refresh ingredients. The recipes tabs includes Briar Heart again. Notice that clicking the Briar Heart ......
Read more >
arango_driver 1.0.0-rc.3 | Dart Package - Pub.dev
ArangoDB driver, working on top of ArangoDB HTTP API. This package is a fork of the dart_arango_min package.
Read more >
Image Layer Details - hyperledger/explorer:1.0.0-rc3
Layer details are not available for this image.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found