Comments (4)
You can always write and register your own custom validator on your custom meta schema.
from json-schema-validator.
But it would work only when the value is present in the input json. If the value doesn't exist, it would just run requiredValidator. We need a custom validator here instead of the predefined RequiredValidator.
Maybe like this gopichandch@d8f00a9
from json-schema-validator.
No that wouldn't be acceptable. I don't see a reason why a custom validator doesn't work. The logic in the PropertiesValidator
that is using the RequiredValidator
is not using it to generate assertions. The RequiredValidator
by itself will be generating the assertions separately, your implementation should be something similar to the RequiredValidator
and you shouldn't be looking at the PropertiesValidator
. Even if it's really required, you can just replace the PropertiesValidator
with your own implementation.
from json-schema-validator.
Related Issues (20)
- Since 1.3.0: IllegalArgumentException instead of JsonSchemaException HOT 1
- Since 1.3.0: $id seems to accept anything HOT 5
- Since 1.3.0: UUID not correctly validated HOT 3
- Since 1.3.0: date not correctly validated HOT 1
- Since 1.3.0: Validation fails on keyword 'uuid' HOT 1
- Since 1.3.0: Warnings for unknown keywords in $defs HOT 6
- Since 1.3.0 - `JsonSchema.getCurrentUri()` missing
- Since 1.3.1: unevaluatedProperties doesn't work with external schemas HOT 3
- Since 1.3.0: URIFactory is gone. Any migration guide? HOT 1
- SchemaValidatorConfig.setLocale(ENGLISH) does not work when running from non-english environments
- Error when resolving "$ref" with "dot slash" paths
- Custom Formats are not allowed for types other than Strings HOT 2
- FailFast Property Does Not Throw JsonSchemaException for Validation Errors in v1.3.1 HOT 3
- Too many errors reported when the "unevaluatedProperties" property is used
- Updating the version for com.networknt json-schema-validator from 1.0.74 to 1.3.2 runs into error for : Reference /definitions/testDocument cannot be resolved HOT 3
- Required validation does not seem to be getting triggered HOT 3
- Unevaluated properties and subschemas HOT 1
- ethlo as an optional dependency?
- Handle Jackson Databind's 'MissingNode' null object better HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from json-schema-validator.