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
In my C# program I try to validate a serialized json string with a json schema via NJsonSchema validator.
Expected behavior: Json string should be validated as correct and not throw an exception.
I tried different online schema validator which showed me that my json string was correct.
Actual behavior: Following exception is thrown: NJsonSchema.Validation.Error : PropertyRequired: #/__referencePath
I don't understand why the $ref isn't recognized as the required porperty anymore and how to fix this.
The C# code as well as the json file and schema are described below. Thanks a lot in advance for your help!
The json schema is summarized in the schema file "schema.txt":
Using $ref as a property name and not a reference propably messes up quite some things (edge case).
Yes it seems like it. But I think it is defined in the JSON Schema standards.
Do you think that this bug can be fixed within the next weeks or do you think it will take longer?
In my C# program I try to validate a serialized json string with a json schema via NJsonSchema validator.
Expected behavior: Json string should be validated as correct and not throw an exception.
I tried different online schema validator which showed me that my json string was correct.
Actual behavior: Following exception is thrown: NJsonSchema.Validation.Error : PropertyRequired: #/__referencePath
I don't understand why the $ref isn't recognized as the required porperty anymore and how to fix this.
The C# code as well as the json file and schema are described below. Thanks a lot in advance for your help!
The json schema is summarized in the schema file "schema.txt":
schema.txt
The json string that has to be validated is summarized in "data.txt":
data.txt
The short code snippet which should illustrate the problem is shown here:
The text was updated successfully, but these errors were encountered: