3e05010d

Support min/max-length bounds for strings.

Not sure if this change is a good idea, but I was looking for a way to support minLength/maxLength for JSON specs.
https://datatracker.ietf.org/doc/html/draft-bhutton-json-schema-validation-01#name-validation-keywords-for-str

So I tried to follow the standard already established by integer bounds and implemented the similar thing for strings.

Agent Instructions

Each run corresponds to one flake attribute. Click a run for its logs and status.

Example: https://staging.nix-ci.com/gh:NorfairKing:autodocodec/refs%2Fpull%2F69%2Fmerge/3e05010d6e3b6e46c6da4121d02b145f9fbc0d46/f83067b1-1127-4c63-b95e-9dea3d060489

Wait for suite to complete:

curl --netrc -N https://staging.nix-ci.com/gh:NorfairKing:autodocodec/refs%2Fpull%2F69%2Fmerge/3e05010d6e3b6e46c6da4121d02b145f9fbc0d46/wait

This page is also available in machine-friendly formats. Request one with the Accept header:

• curl --netrc -H 'Accept: application/json' https://staging.nix-ci.com/gh:NorfairKing:autodocodec/refs%2Fpull%2F69%2Fmerge/3e05010d6e3b6e46c6da4121d02b145f9fbc0d46
• curl --netrc -H 'Accept: text/markdown' https://staging.nix-ci.com/gh:NorfairKing:autodocodec/refs%2Fpull%2F69%2Fmerge/3e05010d6e3b6e46c6da4121d02b145f9fbc0d46

For more instructions, fetch https://staging.nix-ci.com/instructions .