'Must have one or two primary key attributes' when hash and range key defined

[mlcloudsec]

So let's say we have a model definition like this:

`{

identity: 'modelA',

connection: 'dynamoA',

tableName: 'tableA',

attributes: {

    fieldA: {
        type: 'integer',
        primaryKey: 'hash'
    },

    fieldB: {
        type: 'string',
        primaryKey: 'range'
    }
}

}`

The adapter throws 'Must have one or two primary key attributes' because the primaryKeys in the collection.definition is counting the hash and range primary keys and also an id field like so:

`
id: {
type: 'string',
primaryKey: true,
unique: true,
defaultsTo: [Function]
}

`
This happens to be true even with autoPK:false.
Suggestions?