Add branch and stream name validation to schema directives

Schema directives should have additional checks on the input names for branches and streams, if directives can’t be used, validation will have to happen in the resolvers. Below my suggested rules.

Branches Currently implemented in the frontend:

• min length 3 (currently a branch with no name is allowed on the server!)
• max length 25

Optional rules to make branches URL and CLI friendly:

• only lowercase, numbers and dashes
• can’t start with a dash -

Streams Currently implemented in the frontend:

• min length 3
• max length 25

[teocomi]

Alright, didn’t realize 25 is so little! Yes, let’s def go for something higher, 80-100 for a stream name should be enough? Also agree on letting / in the branch names.

[daviddekoning]

If would be interesting to pull all the stream names from hestia to see what the length distribution is (do people rename streams much on hestia?)

I’ll get similar info from our servers, it will be an interesting point of reference.