You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A regular expression pattern should not ideally be used for that as:
Users can find it hard to understand
Can't be reused - there's no way to use a $ref for a regular expression pattern in OpenAPI
Use cases
As an organization API provider
I want to be able to create custom string formats
So I can communicate to the API users the expected format
And I can run the correct validation
Contribution
Are you volunteering for implementing this feature? 👍
The text was updated successfully, but these errors were encountered:
Describe the feature
According to the OpenAPI specification, string "format" is an open value (https://swagger.io/docs/specification/data-models/data-types/#string)
That's also backed by the JSON Schema Specification Draft 2020-12](https://tools.ietf.org/html/draft-bhutton-json-schema-00#section-7.2.3)
The feature request is to support custom "format" fields, not only those defined in the above JSON Schema Specification and implemented on https://github.com/eclipse-vertx/vertx-json-schema/blob/4.4.6/src/main/java/io/vertx/json/schema/impl/Format.java
A regular expression pattern should not ideally be used for that as:
Use cases
As an organization API provider
I want to be able to create custom string formats
So I can communicate to the API users the expected format
And I can run the correct validation
Contribution
Are you volunteering for implementing this feature? 👍
The text was updated successfully, but these errors were encountered: