Crude implementation to allow map values to be part of the check cond… #130
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Basically I have situation where I want to use a value from map type in the schema in the check condition of a updateTransaction function call.
Entity.updateTransaction({ pk: 'TEST', id: details.id, tenantId: details.tenantId, dTimes: { $set: { 'count': { $add: -1 }}}}, { conditions: { attr: "dTimes.count", gt: 0 }})
The condition clause was being generated as
#attr1 > :attr1
This change will generate the clause as
#attr1.#attr11 > :attr1
This probably isn't the best or greatest solution but hopefully it helps explain the problem a little better.
This is a really useful library thank you for the hard work building it.