Skip to content

API Spec Should Provide Source and/or Description of RegEx Validation #3306

Closed
@robscott

Description

@robscott

What would you like to be added:
Ideally the API spec should have more information about RegEx validation, for example where it came from or what it's based on. This should be visible in go type definitions but hidden from the generated CRD.

Why this is needed:
We rely heavily on RegEx validation and it can be difficult to ensure that our validation is well aligned with the relevant RFC or k8s concept. A simple reference or description of how we landed at a specific RegEx would be very helpful for future readers. Since we already have custom CRD gen, it would be relatively simple to build something like this to enable the concept:

startTag := "<gateway:experimental:description>"
endTag := "</gateway:experimental:description>"

Metadata

Metadata

Labels

kind/documentationCategorizes issue or PR as related to documentation.

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions