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
Am adding a custom pattern on a date-time property to override the default DATETIME pattern regex, however, when processing, notice that the default BaseFormatValidatorFactoryFormatValidator still remains in the validator list along with the custom PatternValidatorFactoryPatternValidator that was added.
Is it a bug? Why is the default format validator there, as expected it to be replaced / removed by the custom one.
Version
4.1.2
Context
I encountered an exception which looks suspicious while testing validateSync with a schema.
Do you have a reproducer?
Yes there is a testng but it is in private project, not portable as a public project. But the existing vertx unit test might be enhanced to use a custom date time pattern to see that the default formatter is not removed from the validator list.
pantinor
changed the title
Custom date-time pattern not replacing default pattern
Json Schema usage with a custom date-time pattern is not replacing the default date time regex pattern
Dec 15, 2022
this is an issue related to a component that is not longer maintained and removed in Vert.x 5. Because of this I will close this issue. Feel free to open a new issue, in case this problem also exists in the latest validator.
Questions
Refer to io.vertx.json.schema.common.SchemaImpl which has a list of validators iterated during processing.
https://github.com/eclipse-vertx/vertx-json-schema/blob/master/src/main/java/io/vertx/json/schema/common/SchemaImpl.java#L171
https://github.com/eclipse-vertx/vertx-json-schema/blob/master/src/main/java/io/vertx/json/schema/common/BaseFormatValidatorFactory.java#L103
Am adding a custom pattern on a date-time property to override the default DATETIME pattern regex, however, when processing, notice that the default BaseFormatValidatorFactory FormatValidator still remains in the validator list along with the custom PatternValidatorFactory PatternValidator that was added.
Is it a bug? Why is the default format validator there, as expected it to be replaced / removed by the custom one.
Version
4.1.2
Context
I encountered an exception which looks suspicious while testing validateSync with a schema.
Do you have a reproducer?
Yes there is a testng but it is in private project, not portable as a public project. But the existing vertx unit test might be enhanced to use a custom date time pattern to see that the default formatter is not removed from the validator list.
Steps to reproduce
Extra
The schema am using is this one:
`
The text was updated successfully, but these errors were encountered: