Trevor Eyre

@xcchcaptain Thanks so much for this! Before I merge this PR, I'd like to move this change to the core `packages/autocomplete/AutocompleteCore.js` component, so it can be utilized in both the...

So far this is looking really great, @xcchcaptain! I'm going to try to do a little more testing and get this merged and released this week as v2.1. I'll keep...

@xcchcaptain - I'm trying to test out your changes, but I'm not exactly sure if I'm doing it correctly. I followed along the article below, to try inputting some Japanese...

I'm not sure what the difference is between the CodePen example you linked and the Google search behavior. Can you explain a little more?

Overall I think your approach looks good. For case insensitivity, I think if you find the match indexes with a regex instead of string replace, you could do a case-insensitive...

Are you using the vue component? If so, you can do something similar [to the example for the default slot](https://autocomplete.trevoreyre.com/#/vue-component?id=default-slot).

Ah, in that case you can use the `onUpdate` function to show/hide a no results message. You have to manage it manually, so it's not an ideal solution, but it's...

That's not a bad idea. There are internal `loading` and `loaded` events. I wouldn't be opposed to exposing those as events if you're willing to put up a PR for...

For local development you should be able to `npm start` to run Storybook. By default it starts the JavaScript storybook at `localhost:4003` and the Vue storybook at `localhost:4004`. Then I...

I'm not sure I understand the issue you're having. Do you mean in your `handleLoaded` handler, the `results` argument is not defined? Do you have a branch I could take...