Skip to content
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

Requesting new package name validation tool #435

Open
anchal-physics opened this issue Sep 30, 2024 · 3 comments
Open

Requesting new package name validation tool #435

anchal-physics opened this issue Sep 30, 2024 · 3 comments

Comments

@anchal-physics
Copy link

https://github.com/JuliaRegistries/General/blob/master/README.md#are-there-any-requirements-for-package-names-in-the-general-registry says

There are no hard requirements, but it is highly recommended to follow the package naming guidelines.

But the package naming guidelines do not specify that the package name has to be `Damerau-Levenshtein distance needs to be above 2' for automerging to work. In my opinion, this restriction is too strong and should be set to 1 instead of 2. But even if it is set to 2, we have no pre-assessment tool if the julia package name we are planning for is available and allowed or not. Please provide a tool that runs your automerge requirements on package name on a webpage or somewhere so that we can validate the name.

@carstenbauer
Copy link
Member

Note that "automerge fails" != "the package name is invalid". We make exceptions to the automatically checked rules. But having a way to run the automerge name checks before registration doesn't seem unreasonable to me.

@DilumAluthge
Copy link
Member

Duplicate of JuliaRegistries/RegistryCI.jl#453?

@ericphanson
Copy link
Member

I think it would be cool to have a web tool where you can enter a name and it could run and surface the checks. I don't think it would be worth the increased maintenence cost relative to just providing a function in RegistryCI like JuliaRegistries/RegistryCI.jl#453 though; it seems like something that would end up as nice for a bit until it breaks at some point and goes unmaintained.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants