Feat/search filter

[oskarrough]

Added a type query param to the search route and a <select> to change it. By default it searches everything, like now.

You could argue that it should also be possible to filter in the search-form in the header, but I couldn't find a good UI.

Closes #37

[oskarrough]

Would be nice to move search results to /search/index so the filters don't rerender.

[oskarrough]

Also I wanted to avoid native browser-element but not sure how or why.

oskarrough commented 6 years ago

Here are some different approaches

1. dropdown filter on /search

2. global dropdown filter in header

3. filter as buttons (takes more space but only needs one tap instead of two. also all options are immediately visible)

4www commented 6 years ago

Really nice! I'd go for a combination of options 2 and 3.

It could allow a user to either specifically look for something at search, or filter after for a more detailed option.

We can also imaging that in the dropdown it is not a multiple select, and that on the filter page it could be a multiple select. But i'm not sure this brings so much value (maybe in a later PR if the need is felt).

• © Githubissues.
• Githubissues is a development platform for aggregating issues.

[oskarrough]

Here are some different approaches

1. dropdown filter on /search

2. global dropdown filter in header

3. filter as buttons (takes more space but only needs one tap instead of two. also all options are immediately visible)

[4www]

Really nice! I'd go for a combination of options 2 and 3.

It could allow a user to either specifically look for something at search, or filter after for a more detailed option.

We can also imaging that in the dropdown it is not a multiple select, and that on the filter page it could be a multiple select. But i'm not sure this brings so much value (maybe in a later PR if the need is felt).