Alternative way so specify the search parameters? about docs HOT 6 OPEN

It makes sense, however the frontend should keep the current user friendly way of searching (I took this from Gmail), so the frontend code will need to generate those query params itself.

from docs.

Yes it what I meant, as the frontend provide the params as a field list it feels like it should be doable without too much hassle.

What's your opinion on how to send the params (HTTP params with plain name, use a prefix, something else)?

from docs.

• search[uafter]
• search_uafter

something like this (I already saw both in other apps. It should be able to handle lists as well (like multiple tags).

from docs.

Thanks, it's nice to have a plan, I think I'll maybe try something but I'll have a real look at it when my other PR will be dealt with, to avoid any risk of merge conflicts.

from docs.

As I'm looking at the search code I have troubles understanding what is supposed to happen when a parameter is invalid, for example when a user does not exist: is the search supposed to return nothing at all, or maybe only suggestion ?

from docs.

Also another question: it seems the tools used to generate the API pages don't like ! in parameter name and don't display them, do you have a suggestion to replace !tag?

from docs.