You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While planning work on Issue #49 , I realized that we should restrict and validate package 'tags'. This makes TOML support much more straightforward, and will probably be useful in general if we end up using 'tags' as input to other commands or functionality.
We should use a regex like the following: ^[a-zA-Z0-9]([a-zA-Z0-9_-]*[a-zA-Z0-9])?$
which would allow only alphanumeric characters, underscores, and dashes, while also always starting and ending with an alphanumeric character.
The text was updated successfully, but these errors were encountered:
Closing this in favor of turning 'constraints' into a list of dictionaries, and allowing arbitrary strings in a 'tags' key.
tach init already uses dots by default to tag nested packages, and this is intuitive behavior we should keep. We also use colons in our own 'tach' installation.
While planning work on Issue #49 , I realized that we should restrict and validate package 'tags'. This makes TOML support much more straightforward, and will probably be useful in general if we end up using 'tags' as input to other commands or functionality.
We should use a regex like the following:
^[a-zA-Z0-9]([a-zA-Z0-9_-]*[a-zA-Z0-9])?$
which would allow only alphanumeric characters, underscores, and dashes, while also always starting and ending with an alphanumeric character.
The text was updated successfully, but these errors were encountered: