clojars 2023-01-29

Hey :) Why does a search query with a / in it has to be double url-encoded?

GET /search?q=tools%2Fcli&format=json
This will fail

Thanks for the report! I created https://github.com/clojars/clojars-web/issues/856 to look at it further.

Thanks! Could be a feature or a bug, I'm not sure. I posted in the issue how I currently work around it

Thanks! I'll try to take a look at it this week.

Based on this in your search help: > Note that Clojars stores the namespace and name of a library as separate attributes, so searching for a ns-qualified library will not necessarily return any matches: It seems like splitting / to group-id:... AND artifact-id:... might be a good solution.

This does work:

$ neil dep search org.clojure/tools.cli
:lib org.clojars.rmremizov/clj-argparse :version 0.1.1-SNAPSHOT :description "A convenience wrapper around org.clojure/tools.cli"

But this doesn't:

$ neil dep search org.clojure/tools
Unable to find org.clojure/tools on Clojars.

the first result is also a bit weird

I can compensate for this in neil, but maybe it should be done in clojars?

I think it is because wrapping in quotes tells lucene to match for the exact phrase. And yes, I think clojars should fix this. By > It seems like splitting / to group-id:... AND artifact-id:... might be a good solution. I meant within clojars search implementation.

I think a non-quoted foo/bar would become group-id:foo AND artifact-id:bar, but "foo/bar" would be left alone. You could then remove the quoting in neil, and the searcher would have control over searching as a phrase or not

sounds good

It will succeed when I wrap %22 around it