-
Notifications
You must be signed in to change notification settings - Fork 7.3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Challenge: Search #110
Comments
I'm a big fan of ElasticSearch and would love to see that as well! |
My buddy is swamped at work. I don't see him having the time to take this on in the near future, but I'm sure we can find someone who can. What would be helpful is if there were a spec for what this might look like. Do we only want to support Elasticsearch for now? What about FTS with Postgres or MySQL? What about using a third-party service like Algolia? What should be searchable? Do we want to support multi-faceted search? |
@BRWR I think that an implementation should come first before the spec actually — not all "challenges" will end up needing a spec, but if they eventually do, we'll figure it out down the road and modify the existing implementations |
I don't think I was clear. I'm not looking for a formal spec like the Swagger spec we have for Real World. Just an idea of what this task entails. What features do we want to support? etc. |
Ah gotchya — makes sense 👍 |
Search is the lifeblood of any good app worth its salt. Perhaps we can consider putting up an "extra credit" challenge to add the ability to search text in posts, tags, authors.
The text was updated successfully, but these errors were encountered: