Trevor Eyre

Hmmm, I’m not sure. Could you post the code for the rest of your component. What are you returning from your search function?

I think your problem is that the `search` function should always return something. If you want to return no results, you should return `[]`, but right now you're returning nothing.

Thanks so much for your work on this @versedi. I admit I haven't worked on any substantial project in Typescript. I'd assume it's generally easier to work with if types...

@lastlink I would be willing to support types directly in the repository in the future. I likely won't get to it for a while, but if you'd like to submit...

Yes, this is by design. I know a lot of autocomplete implementations handle this both ways, and I went back and forth a number of times about whether tab should...

@cgosborne I'm going to go ahead and close this. Feel free to re-open if you have additional questions or concerns.

@nextmat Agreed. I'll re-open and add it to the list of use cases to check in v3.

Thanks @mirzaakhena! Using a ref works for now. At some point I do want to make the input value externally controllable via props in v3.

Re-opening this issue so I can address it in v3.

You should be able to define debounce on the root `autocomplete` component like you did here. I'll have to look into why this is happening. There seem to be another...