"Fixed" type attribute should propagate to an empty object member

[Ge11ert]

I'm running on v. 4.0.0-pre.4.

According to MSON Spec, fixed type attribute should propagate to nested members.

First example:

# My API

# Request [GET /first]

+ Response 200 (application/json)
    + Attributes
        + result (object, fixed)
            + obj_member (object)

produces the following schema:

{
  "$schema": "http://json-schema.org/draft-04/schema#",
  "type": "object",
  "properties": {
    "result": {
      "type": "object",
      "properties": {
        "obj_member": {
          "type": "object"
        }
      },
      "required": [
        "obj_member"
      ],
      "additionalProperties": false
    }
  }
}

Second example (obj_member has explicit fixed attribute)

# My API

# Request [GET /first]

+ Response 200 (application/json)
    + Attributes
        + result (object, fixed)
            + obj_member (object, fixed)

produces this (obj_member has field "additionalProperties": false now) :

{
  "$schema": "http://json-schema.org/draft-04/schema#",
  "type": "object",
  "properties": {
    "result": {
      "type": "object",
      "properties": {
        "obj_member": {
          "type": "object",
          "additionalProperties": false
        }
      },
      "required": [
        "obj_member"
      ],
      "additionalProperties": false
    }
  }
}

Expected behaviour:
These 2 examples should generate the same json-schema.

P.S. If obj_member has any nested properties, fixed attribute propagation works correctly.

[kylef]

Thanks for the report @Ge11ert, we'll look into this.

(internal tracking: OACS-5809)

[kylef]

diff --git a/src/refract/ElementUtils.cc b/src/refract/ElementUtils.cc
index f40fca09..1373f720 100644
--- a/src/refract/ElementUtils.cc
+++ b/src/refract/ElementUtils.cc
@@ -38,7 +38,7 @@ bool refract::inheritsFixed(const IElement& e)

 bool refract::inheritsFixed(const ObjectElement& e)
 {
-    return definesValue(e);
+    return true;
 }

 bool refract::inheritsFixed(const ArrayElement& e)

The above patch would fix this particular case, but not sure what else it could break.

[kylef]

@Ge11ert We've released a fix in Drafter 4.0.0-pre.6.