🚀 Deployed on https://5f49651ee28abe00aa84b74a--nixos-search.netlify.app

It looks like it may be filtering results way better, for some of the queries. css minifier decreases from 559 to 192 results.

Though, at the same time, there are still high ranking results that I doubt should be present. Right after the perl-based CSS minifier results, there are JavaScript minifiers, nothing matching CSS AFAICT.

• https://5f49651ee28abe00aa84b74a--nixos-search.netlify.app/packages?show=perl528Packages.JavaScriptMinifierXS&query=css%20minifier&from=0&size=15&sort=relevance&channel=unstable

I don't understand what the implementation changes here are, considering my lack of expertise with Elasticsearch. So I can't say for sure whether this is going in the right direction, though observing the effects it seems it does.

Is it possible to see why a result was matched in the result? Is this what matched_queries represent? And then it's ranked (only?) by the amount of matched queries? I see it goes from 20 for the first two, while going to 9 from then on. I can see the same names under should in the query.

It looks like it may be filtering results way better, for some of the queries. css minifier decreases from 559 to 192 results.

Though, at the same time, there are still high ranking results that I doubt should be present. Right after the perl-based CSS minifier results, there are JavaScript minifiers, nothing matching CSS AFAICT.

* https://5f49651ee28abe00aa84b74a--nixos-search.netlify.app/packages?show=perl528Packages.JavaScriptMinifierXS&query=css%20minifier&from=0&size=15&sort=relevance&channel=unstable

I don't understand what the implementation changes here are, considering my lack of expertise with Elasticsearch. So I can't say for sure whether this is going in the right direction, though observing the effects it seems it does.

I'm thinking of merging this since it immediately improves things, but trying to rethink and improve further.

Is it possible to see why a result was matched in the result? Is this what matched_queries represent? And then it's ranked (only?) by the amount of matched queries? I see it goes from 20 for the first two, while going to 9 from then on. I can see the same names under should in the query.

in both Packages.elm and Options.elm you can look for -- DEBUG: and if you comment out those lines it will print which queries are matched. Also the matching score is then displayed for each result. This is what I usually uncomment when I'm working on figuring out the relevancy.

But you don't have to worry with Elm, you just need to type JSON as described in https://www.elastic.co/guide/en/elasticsearch/reference/7.2/query-dsl.html . then you simply issue a curl request.

🚀 Deployed on https://5f4a9daf86e5376d75edb317--nixos-search.netlify.app

🚀 Deployed on https://5f4ace355bf9307d47ad337c--nixos-search.netlify.app

🚀 Deployed on https://5f4ad0eea0882983707b0af2--nixos-search.netlify.app

🚀 Deployed on https://5f4ad3c2a08829ce677b0c22--nixos-search.netlify.app

🚀 Deployed on https://5f4ad41846d5ad773b178b09--nixos-search.netlify.app