Document Constraint Types in Code

[georg-schwarz]

This mechanism is similar to the current jv code generation to self-document blocktypes.

Exerpt:

I noticed some issue with Jayvee having no concept for INFINITY. Still, I'd vote to integrate this feature nevertheless.

[rhazn]

If I understand this right this introduces builtin constraintypes without added logic and parses the ones from our Typescript code into a simulated stdlib jayvee code, right? If so, sounds like a good first step, mediumterm I think it would be good to go from actual jv code to our metainf.

I disagree on the Infinity being okay though, I think we should never generate invalid jayvee code. I left a comment on how I think we can avoid that. Otherwise I am happy with this.

[georg-schwarz]

If I understand this right this introduces builtin constraintypes without added logic and parses the ones from our Typescript code into a simulated stdlib jayvee code, right? If so, sounds like a good first step, mediumterm I think it would be good to go from actual jv code to our metainf.

Correct. It is the first step towards turning the mechanism around. The idea is to have this syntax as comparison now to the meta-inf in order to see what else we need to go this step. I think the only thing we need is to express validations that concern multiple properties of the constraints (e.g., minLength <= maxLength).

I disagree on the Infinity being okay though, I think we should never generate invalid jayvee code. I left a comment on how I think we can avoid that. Otherwise I am happy with this.

Done!