Skip to content

Conversation

@rambleraptor
Copy link
Contributor

I noticed that we have several UUID fields in the REST Catalog that are just basic strings. Moving them over to UUIDTypeValue shows the proper validation + proper context, especially to OpenAPI tools that are consuming the spec.

This change should be a no-op, since these UUID restrictions already existed, but were never documented.

@manuzhang manuzhang changed the title Change UUID fields from string type to UUIDTypeValue Spec: Change UUID fields from string type to UUIDTypeValue Jan 21, 2026
maximum: 3
table-uuid:
type: string
$ref: '#/components/schemas/UUIDTypeValue'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for other reviewers: this shouldn't break any spec guarantees because UUIDTypeValue is defined to be string in

UUIDTypeValue:
type: string
format: uuid
pattern: '^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$'
maxLength: 36
minLength: 36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants