bug: nested defaults will not be applied

[lgersman]

If a json schema provides nested defaults like this schema :

{
  "title": "Schema default properties",
  "type": "object",
  "properties": {
    "valuesInFormData": {
      "title": "Values in form data",
      "$ref": "#/definitions/defaultsExample"
    },
    "noValuesInFormData": {
      "title": "No values in form data",
      "$ref": "#/definitions/defaultsExample"
    }
  },
  "definitions": {
    "defaultsExample": {
      "type": "object",
      "properties": {
        "scalar": {
          "title": "Scalar",
          "type": "string",
          "default": "scalar default"
        },
        "array": {
          "title": "Array",
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "nested": {
                "title": "Nested array",
                "type": "string",
                "default": "nested array default"
              }
            }
          }
        },
        "object": {
          "title": "Object",
          "type": "object",
          "properties": {
            "nested": {
              "title": "Nested object",
              "type": "string",
              "default": "nested object default"
            }
          }
        }
      }
    }
  }
}

json-schema does not apply these defaults using Constraint::CHECK_MODE_APPLY_DEFAULTS flag.

only top level defaults will be applied.

[COil]

Hello @lgersman, we are facing the same issue. In fact, it works for nested properties of objects but it doesn't work for array types.

[DannyvdSluijs]

@lgersman I see this report have been left unanswered very long, that is on us. I'm however trying to wrok through the lisst of reports and I'm trying to resolve this one.

In reading the JSON Schema specification about defaults and one thing that seems important in this is:

It is RECOMMENDED that a default value be valid against the associated schema.
This is also reflected in code and thus intentional once a default value has been applied no defaults of deeper properties is applied. Some debugging also confirmed nested defaults are not applied by design.

In your schema there is no default for #/definitions/defaultsExample. Setting a valid default (so including properties and values for all properties of the #/definitions/defaultsExample definition on that level would resolve your problem.

Closing as "Not planned" in cause you've any additional information feel free to let us know more and reopen this report.