Add constraints to #Lineage.name

[sdboyer]

At minimum, we want:

• strings.MinRunes(1)
• ~=[z-aA-Z0-9_]

Probably the ideal target is the set of valid characters for an unquoted CUE label. That covers another known, future use case by disallowing slashes - important to be able to introduce e.g. an optional #Lineage.uri property later, and enforce that its trailing element is == #Lineage.name and be able to know a priori that there is only one trailing element.

Again, we can open this up more later. Opting for restrictiveness initially gives us more options later.

[verdverm]

I've been thinking about restricting some names in hof in a way that matches k8s & DNS Label Names. Should be something like:

name: =~ "^([[:alpha:]][[:alnum:]-]{0,61}[[:alnum:]]|[[:alpha:]])$"

https://cuelang.org/play/?id=kuNNBpN464J#cue@export@cue

https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-label-names

One thing to consider is that if you are mapping these names to filenames or paths, Mac does not distinguish between upper & lower case.

[sdboyer]

Oooh, that's helpful.

i was already thinking i'm gonna end up having to allow -. That one actually works less well than underscores for generated symbol names, where most languages disallow it - but for a name, i think that's probably less important. (It also screwed up the logic in Thema for internally generating a def of each schema in the lineage, for closed validation purposes.)

That doing dashes but not underscores aligns with dns naming and k8s makes the path here seem pretty clear.

also

[:alpha:]][[:alnum:]

Mmm, for a schema that's likely to be frequently read by human eyes, i definitely do like using the named ASCII character classes more than writing them out raw.