Model with deep object references is truncated

[makered]

If I have the following model:

{
    "Job": {
        "id": "Job",
        "properties": {
            "col1": {
                "$ref": "B"
            }
        }
    },
    "B": {
        "id": "B",
        "properties": {
            "col2": {
                "$ref": "C"
            }
        }
    },
    "C": {
        "id": "C",
        "properties": {
            "col3": {
                "type": "array",
                "items": {
                    "type":"string"
                }
            }
        }
    }
}

It will get presented in the UI as:

{
  "col1": {
    "col2": "C"
  }
}

Note how the C object is not rendered.

If I take the same model and add C as a child of Job as well:

{
    "Job": {
        "id": "Job",
        "properties": {
            "col1": {
                "$ref": "B"
            },
            "col4": {
                "$ref": "C"
            }
        }
    },
    "B": {
        "id": "B",
        "properties": {
            "col2": {
                "$ref": "C"
            }
        }
    },
    "C": {
        "id": "C",
        "properties": {
            "col3": {
                "type": "array",
                "items": {
                    "type":"string"
                }
            }
        }
    }
}

Then I get the following with C parsed in both locations:

{
  "col1": {
    "col2": {
      "col3": [
        ""
      ]
    }
  },
  "col4": {
    "col3": [
      ""
    ]
  }
}

Seems like I am hitting some kind of a nesting limit bug?

Thanks,

[fehguy]

deep nesting should be supported just fine. Can you post your whole JSON file?

[makered]

The example I gave is actually the complete model I am using and is what I had issues with, only changed label names.

[webron]

I think Tony wanted to see the full JSON including the operations...
probably for testing purposes.

On Thu, May 15, 2014 at 9:02 AM, Ed Levin [email protected] wrote:

The example I gave is actually the complete model I am using and is what I
had issues with, only changed label names.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/463#issuecomment-43171449
.

[makered]

Oh, sorry. I was just doing a test so not much content:

var param, sw, swe;
sw = require("swagger-node-express");
param = sw.params;
swe = sw.errors;
exports.addJob = {
  'spec': {
    description: "Add a job",
    path: "/v1/job",
    method: "POST",
    summary: "Add a job",
    notes: "Add a job",
    nickname: "addJob",
    produces: ["application/json"],
    parameters: [param.body("Job", "Job object", "Job")],
    responseMessages: [swe.invalid("job")]
  },
  'action': function(req, res) {
    return res.send(200);
  }
};

Also running swagger-node-express 2.0.2 and swagger-ui 2.0.16

[GStipick]

I am running into this issue as well.
After doing some testing, I am noticing that there is a possible cap where nesting of $ref models only goes 1 deep. makered's 2nd example worked is since the 'Job : col4' property directly calls the 'C' model from 1 layer deep. Since that model is loaded, it is then used to fill in the blanks for the 2nd nested layer 'Job : col1 -> B : col2' reference to the 'C' model.
Not sure if this is a swagger-ui problem or a swagger-js/swagger-node-express problem.
Using swagger-node-express 2.1.0 (with packaged swagger-ui)
Commit: [97e265e]
Date: Wednesday, July 16, 2014 5:53:33 PM

[fehguy]

I believe this is fixed in M1, but will verify and close in M2.

[fehguy]

fixed in 21d8a89

[johncrim]

I'm seeing ulong values rounded off - could this be the same issue, or is it a new one?

Eg value 7286923155816383186 in my JSON is rounded to 7286923155816383000 in the UI.

I'm using "Swashbuckle.Core" version="5.3.2", so don't know what version of swagger this translates to.

[webron]

@johncrim - no, that's #2030.