David Alberto Adler
David Alberto Adler
Sorry to bother you. Would really appreciate some insight here on a recommended approach. I've looked into this batching thunk issue but it doesn't seem to have any effect on...
Any update on this one? Would be such a great feature as otherwise we lose all the awesome aliasing features in the deeper nested maps 😢.
Yeah in my case I couldn't use an object as I needed the selective updates as you say.
As for the deep updates... I created this - if it's of any use ```js const get = require('lodash/get') const set = require('lodash/set') const { documentClient } = require('@shared/documentClient') const...
did the dot notation issue ever get fixed?
``` await Group.put({ pk, enabled: true }) { TableName: 'Group', Key: { pk: 'asdf', }, UpdateExpression: 'SET #createdAt = if_not_exists(#createdAt,:createdAt), #updatedAt = if_not_exists(#updatedAt,:updatedAt), #enabled = :enabled', ExpressionAttributeNames: { '#createdAt': 'createdAt',...
Interestingly using `enabled: () => false` works instead of `enabled: false` using the former: ``` { TableName: 'Group', Key: { key: 'asdf', }, UpdateExpression: 'SET #createdAt = if_not_exists(#createdAt,:createdAt), #updatedAt =...
Using version 0.2.0-beta.1 FYI 💁♂️
Ah okay yeah makes sense. Shouldn't the toolbox then throw `if (key in payload) { assert(payload[key] !== undefined, 'use $remove')`
Well yeah, but if it has meaning then it should do something, otherwise it's an unknown parameter. Anyway, I don't feel that strongly about this, happy for it to be...