Validation inconsistencies for overridden properties for referenced schemas.

[ajmalrahman]

I have the following schema (internal-msg.yaml) that I use to validate using the json-schema-validator :

{
   "title":"InternalMessage",
   "type":"object",
   "allOf":[
      {
         "$ref":"public-msg.yaml"
      },
      {
         "properties":{
            "id":{
               "readOnly":false
            },
            "status":{
               "type":"boolean"
            }
         },
         "required":[
            "id",
            "status"
         ]
      }
   ]
}

The public-msg.yaml also has the field id that I wanted to override in my internal-msg.yaml. And when loading the schema (as pasted above) - it does seem like it is overridden.

But when I try to validate the json that has the id against the schema, it still does not expect an ID there and complains that it is a readOnly property that cannot be changed.

Why is this happening? I think the schema definition is correct, so probably the validator is not handling the overrides correctly?

[stevehu]

Close as there is no activity.