Hello,
Thanks for the article suggestion.
It indeed does what I want to achieve as well.
I compared their logic with mine, and I have to say it’s pretty much the same (except for my build_search_query etc that you mentioned).
I tried to play around with the code to make it look more like theirs, but that did not help much.
As well as using ~p"/search?#{params}"
What I see is that in the article they only have string params, while I have lists.
It all works with just the search query (which is string), until I start trying to parse lists too.
Even ~p"/search?#{params}" returns string like "search/?query=test&f1[]=value1&f1[]=value2", whereas I would expect something like "/search?query=test&f1=value1,value2"
it’s likely you will find the booleans are becoming strings, ie
"false"rather thanfalsein theparamsof yourhandle_params.
I don’t have booleans yet anywhere, just string query (which works fine) and lists of strings for filters.
