Haxelib Project/User/Tag Name Restrictions about haxelib HOT 2 CLOSED

Library name is currently checked to be 3 characters Data.doCheck()
The checks for username (3 chars, alphanumeric) are in Repo.register()
Tags are currently only tested in Data.doCheck(), and the only test is
that they are a string.

I agree with adding the extra restrictions, as documented.

The length checking for each happens separately at the moment, so I don't
mind tags being 2 characters and project names / user names being more. I
also don't mind standardizing it. Pretty indifferent really.

As for extra characters, maybe I'm a punk english-only speaker that rarely
needs anything outside [a-z0-9_.-], but my leaning is towards "no". The
names have to be used in URLs, in Haxe code (#if mylib) and in hxml files /
command line params, as well as by haxelib itself. I think there's a lot
of room for things to go wrong, for parsers to be unhappy, or for things to
get hard to type.

Jason

On Fri, Jun 14, 2013 at 10:02 AM, Zachary Dremann
[email protected]:

According to the haxe documentationhttp://haxe.org/doc/haxelib/using_haxelib#creating-a-haxelib-package,
We place some restrictions on the name/user, specifically:

• Length must be >= 3
• All characters must be one of [A-Za-z0-9_-.]

I could find no such restrictions on tags, on the site, or in the haxelib
code (but I definitely could have missed it). I think we should place
similar restrictions on tags as we place on user names and project names.
We need to decide: What restrictions should we place on tag names?

I think we should use the same character restrictions everywhere. Easier
for us, and easier for users, and I don't think it's too restrictive. Tags
need to be at least down to 2 characters long, to support current tags like
'js' and 'cs'.
Do we want to change any of the rules for projects/user names?

• We could allow more characters (accents, other symbols. e.g. A*pathor C--
  proj).
• We could change the minimum length to two. This allows for the same
  verification for tags, projects, and user names.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/61
.

from haxelib.

Okay, I'm saying we go with

Tag Name

[A-Za-z0-9_.-]{2,}

User Name

[A-Za-z0-9_.-]{3,}

Project Name

[A-Za-z0-9_.-]{3,}

Exactly the same as we had, except for tags, which now get some restrictions beyond being a string.

from haxelib.