node/lib/kpl-deagg.js uses camelCase for sequenceNumber and subSequenceNumber. Currently, the mismatch means that UserRecord.sequencenumber and UserRecord.subSequencenumber are undefined
The explicitHashKey should be optional, because it is not a required parameter of a PutRecord nor PutRecordRequestEntry. Making it optional in the interface means that expected UserRecord with undefined explicitHashKey can be used in tests and code.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Issue #, if available:
possibly #48
Description of changes:
sequencenumbertosequenceNumbersubSequencenumbertosubSequencerNumberexplicitHashKeyoptionalWhy?
node/lib/kpl-deagg.jsuses camelCase forsequenceNumberandsubSequenceNumber. Currently, the mismatch means thatUserRecord.sequencenumberandUserRecord.subSequencenumberare undefinedThe
explicitHashKeyshould be optional, because it is not a required parameter of a PutRecord nor PutRecordRequestEntry. Making it optional in the interface means that expectedUserRecordwith undefinedexplicitHashKeycan be used in tests and code.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.