Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autowhatever require specific props ?? #738

Closed
thomaslc66 opened this issue Apr 26, 2020 · 6 comments
Closed

Autowhatever require specific props ?? #738

thomaslc66 opened this issue Apr 26, 2020 · 6 comments
Labels

Comments

@thomaslc66
Copy link

Are you reporting a bug?

Don't know, but seems like an odd behavior

I've not set multiSection={true}
My code look like this :

        <Autosuggest
          suggestions={suggestions}
          onSuggestionsFetchRequested={onSuggestionsFetchRequested}
          onSuggestionsClearRequested={onSuggestionsClearRequested}
          getSuggestionValue={this.getSuggestionValue}
          renderSuggestion={renderSuggestion}
          onSuggestionSelected={this.onSuggestionSelected}
          inputProps={inputProps}
        />

But in the console i have those 2 messages, but i don't need multiSection and even if i set multiSection={false} the error is still the same

image

@masbaehr
Copy link

Same issue recently needs to be fixed please

@aberezkin
Copy link
Collaborator

Working on it.

@aberezkin aberezkin added the bug label Apr 27, 2020
@tpenaranda
Copy link

As a workaround @thomaslc66, adding "empty" functions on renderSectionTitle and getSectionSuggestions props did the trick for me.

<Autosuggest
  ...
  renderSectionTitle={() => {}}
  getSectionSuggestions={() => {}}
/>

@jscul
Copy link

jscul commented Apr 28, 2020

tpenaranda's suggestion didn't fix the issue. Even if I put multiSection={false}. No luck. Downgrading to "react-autosuggest": "^9.4.3" fixes the issue for now.
Thanks for contributing @aberezkin.

@adriancorcoran
Copy link

@tpenaranda Solution worked also, empty functions are the way to go to solve this for now

@aberezkin
Copy link
Collaborator

Fixed in v10.0.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants