Allow for greater flexibility for defining properties in a JSON Collection

[DreamingInBinary]

Take this simple JSON response:

{
    "success": true|false,
    "error": {
        "message": "string",
        "code": "string",
        "details": {
            "error": "string"
        }
    }
}

As it stands now with Plank, you can define the success property easily within one model, but the dictionaries in the response leave you with either having to use a Map type (which more or less kills the power of Plank for me as I don't want to do something like errorModel[@"details"][@"error"]) or create another model to reference for error and details. Creating another model gives me the type safety I'm after, but at the same time it's also time consuming and a bit overkill.

It'd be create if we define properties by keying them via the dictionary like Mantle allows, something like this for the example above:

{
"id": "errorDetails.json",
"title": "errorDetails",
"description" : "Schema definition of Reply Error",
"$schema": "http://json-schema.org/schema#",
"type": "object",
"properties": {
	"success" : { "type": "boolean" },
	"error.message" : { "type": "string" },
	"error.code" : { "type": "string" },
            "error.details.error": { "type": "string" }
}

}

Unless I'm missing something, I don't think that's possible today with Plank. Either way, keep up the great work!

[rahul-malik]

Definitely not possible with plank today but this is approaching a more generalized way to have simpler concrete types defined alongside the parent type

This does seem convenient but if we did this I would imagine we could just inline the definition of the new schema vs putting it in a separate file. Thoughts?

[ay8s]

@rahul-malik That'd be super useful, we have a few cases already where we could simplify things a bunch if you could inline the definition.