[BUG] Schema option `saveUnknown` is not working for an array

Summary:

Setting the Schema option saveUnknown to true works as expected, but using an array does save empty objects into DynamoDB:

           const catSchema = new dynamoose.Schema({
                name:          String,
                something:     Object,
                somethingElse: Object,
            }, {
                saveUnknown: [
                    'something',
                    'somethingElse',
                ],
            });
            const catModel       = dynamoose.model('Cat', catSchema);

            const cat = {
                name:          'Test',
                something:     {
                    hello: 'world',
                },
                somethingElse: {
                    hello:   {
                        world: 'hello!',
                    },
                    anArray: [1, 2, 3, 4],
                }
            };

            await catModel.create(cat);

aws:dynamodb:putItem:request - {
    "Item": {
        "name": {
            "S": "Test"
        },
        "something": {
            "M": {}
        },
        "somethingElse": {
            "M": {}
        }
    },
    "TableName": "Cat",
    "ConditionExpression": "attribute_not_exists(#__hash_key)",
    "ExpressionAttributeNames": {
        "#__hash_key": "name"
    }
}

[MickL]

So the problem was that saveUnknown only effects the first layer. In my case wildcards * and ** should have been used as stated in the docs.

[fishcharlie]

@chadlittle Sounds good. Keep in mind, it’s also better to set the schema property as opposed to saveUnknown. That way it’s more clear what is actually being saved. I’d only recommend saveUnknown for cases when you truly don’t know what you are saving or what your schema looks like.