Bug in sub object property with required keyword

[amazing-gao]

Hi, i find a bug of the schema which has sub object with required property.
Such as, manage has a required field startAt and endAt, but i get the jsonschema with required properties name,internalName,startAt,endAt at the top level.
This will make validation failed to JSON-SCHEMA 4.
Do you have time to fix it?
Thanks.

// mongoose schema
{
    name: {
        type: String,
        required: true,
        unique: true,
    },
    description: {
        type: String,
    },
    internalName: {
        type: String,
        required: true,
        unique: true,
    },
    manage: {
       offline: { 
            type: Boolean,
            default: true,
        },
        startAt: {
            type: Date,
            required: true,
        },
        endAt: {
            type: Date,
            required: true,
        },
    },
}

// jsonschema
{
    "title": "book",
    "type": "object",
    "properties": {
        "name": {
            "type": "string"
        },
        "description": {
            "type": "string"
        },
        "internalName": {
            "type": "string"
        },
        "manage": {
            "title": "manage",
            "type": "object",
            "properties": {
                "offline": {
                    "type": "boolean",
                    "default": true
                },
                "startAt": {
                    "type": "string",
                    "format": "date-time"
                },
                "endAt": {
                    "type": "string",
                    "format": "date-time"
                }
            }
        }
    },
    "required": [
        "name",
        "internalName",
        "startAt",
        "endAt"
    ]
}

[DScheglov]

thank you, taking to investigation.
will back with solution soon (2017-03-25)

[DScheglov]

Fixed
See test-suite:
https://github.com/DScheglov/mongoose-schema-jsonschema/blob/master/test/suites/required-issue.js

[amazing-gao]

I have upgraded to 1.1.12 version and the bug was fixed.
I really appreciate what you have done.