A DynamoDB library to ease the use of modeling complex hierarchical relationships and implementing a Single Table Design while keeping your query code readable.
MIT License
956
stars
58
forks
source link
Collection validation should check `field` property of composite attributes #394
Describe the bug
When defining a collection, ElectroDB validates composite attributes without checking the field property. Since collections map to DynamoDB queries, and composite key attributes are mapped to DynamoDB names using the field property if it's specified, the collection validator should take this property into account.
ElectroDB Version2.14.1
ElectroDB Playground Link
N/A
Entity/Service Definitions
Include your entity model (or a model that sufficiently recreates your issue) to help troubleshoot.
Describe the bug When defining a collection, ElectroDB validates composite attributes without checking the
field
property. Since collections map to DynamoDB queries, and composite key attributes are mapped to DynamoDB names using thefield
property if it's specified, the collection validator should take this property into account.ElectroDB Version
2.14.1
ElectroDB Playground Link N/A
Entity/Service Definitions Include your entity model (or a model that sufficiently recreates your issue) to help troubleshoot.
Expected behavior The collections schema validator should check the
field
property during schema validation and the above should succeed.Errors