Extract conan vrange registration to separate directory
What does this MR do?
Conan vrange handling is currently done by the npm vrange handling script. This is fine, but it's very unclear in the code—you have to go to vrange/npm/npm.go
to see this when going over the code. It would be clearer if Conan maintained the same format as other runtimes and had its own separate directory and conan.go
file, even if the file just registers it under the npm rangecheck
script. It makes the structure clearer and reduces the likelihood of the thought "wait, don't we also support Conan? Where is it?" occurring (that's what happened to me initially).
What are the relevant issue numbers?
Does this MR meet the acceptance criteria?
-
Changelog entry added -
Documentation created/updated for GitLab EE, if necessary -
Documentation created/updated for this project, if necessary -
Documentation reviewed by technical writer or follow-up review issue created -
Tests added for this feature/bug -
Job definition updated, if necessary -
Conforms to the code review guidelines -
Conforms to the Go guidelines -
Security reports checked/validated by reviewer
Edited by Yasha Rise