Misha Moroshko
Misha Moroshko
Could you create a Codepen that reproduces the issue, please?
Could you include the link to the guidance?
Sorry, I'm not an accessibility expert. If anyone has a concrete suggestion how to make the Autosuggest more accessible, I'll happily accept a PR.
It's hard to say from the information you provided what's wrong. This error could appear if somehow `inputProps.value` ends up not being a string. Could you verify that it is...
@Mateusz-Czarnik Could you create a Codepen that reproduces the issue?
Thanks for the issue 👍 Looks like a bug! I guess it's probably related to `alwaysRenderSuggestions` being `true`, because this is the only example there that sets it to `true`,...
I'd just add the section info to each suggestion, and use it in `renderSuggestion`, e.g.: const suggestions = [ { text: 'France', sectionType: 'country' }, { text: 'Watermelon', sectionType: 'fruit'...
@olance OK, this makes sense! Would you like to contribute a PR? (Note it will conflict with https://github.com/moroshko/react-autosuggest/pull/384)
I'm not sure I understand the issue with `renderSuggestionsContainer`. The `children` you get in this function are already rendered using `renderSuggestion`. So, if we add `section` to `renderSuggestion`, wouldn't this...
At this point, we expose a single `Autosuggest` component, which is a [controlled component](https://reactjs.org/docs/forms.html#controlled-components). You can think about it as a low level API. We could definitely explore exposing a...