Skip to content
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

Text search should let the user find all libraries based on language #28

Open
bobylito opened this issue Jun 8, 2017 · 7 comments
Open

Comments

@bobylito
Copy link
Contributor

bobylito commented Jun 8, 2017

For example if I type JS, I will only get the JS API client. I want to be able to find instantsearch.js and react-intstantsearch.

@rayrutjes
Copy link
Member

I think this would be solved by #26 + #27, any opinion on those @bobylito ? especially #27 ?

@bobylito
Copy link
Contributor Author

bobylito commented Jun 8, 2017

I think they go in the same direction, but they are on different search path for the user. I might prefer clicking on a language or just type JS in the search field. They're both as valid, don't you think @rayrutjes ?

@rayrutjes
Copy link
Member

Ah yes, I see what you mean now, I agree that making the language a searchable attribute would be awesome!

@Shipow
Copy link
Contributor

Shipow commented Jun 11, 2017

@bobylito
Copy link
Contributor Author

any edit of this file is welcome! :)

Good to know, will do! However I think it's in the index config that we can solve that :)

@Shipow
Copy link
Contributor

Shipow commented Jun 12, 2017

https://github.com/algolia/algolia.github.io/blob/source/config.json is pushed to algolia when the project is build.

@Haroenv
Copy link
Contributor

Haroenv commented Aug 8, 2017

Now when you type, only expect JSX is returned. Did we stop searching and displaying the other attributes? 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants