Decide on how we want to model filtering issues and repos

[rashadg1030]

By @chshersh:
Though, it's an open question, how do we want to model filtering. For example, when a user enters labels difficulty:easy and difficulty:medium does he want to have issues that have both labels easy and medium or any of the labels? In this case, probably the first. But what if here enters difficulty:easy and refactoring? Maybe now he wants to have these two labels. We can't read the user's mind so we either will stick to one default or support both strategies. Not now, just something to think about.

[sshine]

Would it make sense to group search terms, and for each group imply an operator, and between groups imply AND? For example, for difficulty it would be OR, and for search terms it would be either AND or some smart/fuzzy matching if the API allows it.

[rashadg1030]

@sshine Thank you for your input. If I understood your comment correctly, you suggest that we support both AND and OR for queries. I agree that we support both as well.