-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
feat: Use Algolia Docsearch #163
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for guidemaker-ember-template ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
||
export default Component.extend({ | ||
layout, | ||
|
||
classNames: ['search-input'], | ||
|
||
searchService: service('search'), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This service can likely also be removed, but unclear if that would be a breaking change for consumers of this package.
Tested this locally on I wonder if this is a backend thing that's not compatible with the indexes? Should this be registered separately? https://docsearch.algolia.com/apply/ |
Switches from the current custom built components to the premade Docsearch components by Algolia.
The biggest benefit would be accessibility: these components are fully keyboard accessible.
ref:
https://github.com/algolia/docsearch