-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
depends-on search seems broken #911
Comments
Thanks for opening this issue! We, the Scala Center team, reworked the architecture of the Scaladex backend, and along the way we decided to leave some features behind, included this one. I will be happy to bring it back, but I would like to suggest some changes in the definition of the feature itself. 1. Ambiguity of artifact nameThe artifact name alone ( But this table below shows that some artifact names are used by many organizations: So the artifact name alone is not enough: we should also have the group_id:
2. Searching for projects or artifactsHere it seems you want to find all projects that have at least one artifact that depends on another artifact whose name is akka-actor. So the criteria is Alternatively it could be To distinguish between the two we should call the parameters Your example would become 3. HTTP query parameterI also suggest we use HTTP query parameters rather than the search query. They are easier to document and to type-check in the code. Finally the request would be:
Or
|
If it is not supported anymore we can/should remove the "Artifact Dependents"-link on the detail page of projects. |
The 'Artifact dependents' is always empty for me, i.e. https://index.scala-lang.org/search?q=depends-on%3Aakka-actor should give some results.
The text was updated successfully, but these errors were encountered: