feat: migrate to autocomplete.js v1 [BREAKING CHANGES]

[bodinsamuel]

Closes #76

Changes

• Complete migration to autocomplete v1
• New option for theming
• algoliasearchNetlify() will throw if missing mandatory option
• the UI has a minimum of 400px width

How to migrate

• autocomplete.js now creates its own input, so we no longer support input selector.
  solution: remove your input, create an empty node, e.g:<div id="#search"></div> and use selector: "#search"
• color property has been removed in favor of theme for improved theming ability.
• silenceWarnings has been removed
• autocomplete property has been removed in favor of selector and hitsPerPage at the top level
• ui no longer adapt to size of the input and follow autocomplete.js panelPlacement: 'input-wrapper-width', to improve this behavior you can adapt the CSS on your own with media queries.

[sbellone]

Looks promising!
Main issue is that the results are not closed when we click away and stay open forever.

[francoischalifour]

Main issue is that the results are not closed when we click away and stay open forever.

@sbellone That's because the debug option is used in development in your integration. I wouldn't recommend using it as a default though, as it's mostly useful to inspect the results panel when templating your items. It shouldn't be used in production—in fact, you should see a warning.

We talk about this in the "Debugging" section of our docs.

[bodinsamuel]

• Disabled openOnFocus and added an option
• Added option for placeholder
• Fixed poweredBy
• Fixed types

[sbellone]

🚀

[sbellone]

I've just found out that it doesn't work correctly if the index has no attributesToSnippet (only the title is displayed in that case).
The current version of the UI is requesting them at runtime, I think this new version should do the same.

[bodinsamuel]

if the index has no attributesToSnippet

All Netlify indices are pre configured with attributesToSnippet by default

[sbellone]

All Netlify indices are pre configured with attributesToSnippet by default

Automatically? That's not what I have observed. They currently have content as attributesToSnippet because we set it in the initial index settings, but that's it.
Here your UI expect description to be snippeted and it's not the case by default so the description will never be displayed until the users put it as an attribute to snippet. It fallbacks on the content.

What's the problem of sending them at runtime just in case since we rely on them for the display?

[bodinsamuel]

Here your UI expect description

ah, we should just change our default index settings then.

[sbellone]

Ok but we can also have the UI fallback to the actual fields if no snippetting available, to not have the UI broken because of index settings

[bodinsamuel]

to not have the UI broken because of index settings

Did the change but index settings are very tied to the UI, they change it they assume it imo.

[sbellone]

True, so a fallback on raw fields if no snippets available permits to let user controlling the length of the snippets actually. As you prefer!