Clarify repo name regex intention
Add context to comment to explain the repo name regex in addition to describing it. Signed-off-by: David Warshaw <david.warshaw@gmail.com>
This commit is contained in:
parent
53e18a9d9b
commit
32c77af6ac
1 changed files with 5 additions and 1 deletions
|
@ -9,7 +9,11 @@ var (
|
|||
|
||||
// separatorRegexp defines the separators allowed to be embedded in name
|
||||
// components. This allow one period, one or two underscore and multiple
|
||||
// dashes.
|
||||
// dashes. Repeated dashes and underscores are intentionally treated
|
||||
// differently. In order to support valid hostnames as name components,
|
||||
// supporting repeated dash was added. Additionally double underscore is
|
||||
// now allowed as a separator to loosen the restriction for previously
|
||||
// supported names.
|
||||
separatorRegexp = match(`(?:[._]|__|[-]*)`)
|
||||
|
||||
// nameComponentRegexp restricts registry path component names to start
|
||||
|
|
Loading…
Reference in a new issue