You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe Tesseract.remove could take an array of indices as well as a single index?
Tesseract.remove(state.cards,cardIndexes)
We were also talking about batch updates the other day, this would be a very good use case for them. I expect that I want my removal of the list and it's associated cards to all happen in one transaction as opposed to individual actions:
I'm not sure it's worth adding the additional API surface area for this particular case (I think looping over the cards within a changeset block is not really that bad). Moreover, the transaction block won't actually guarantee that you won't end up with a card referencing a nonexistent list, because another user could concurrently add a card to the list without being aware that it is being deleted.
I'll close this issue, and instead open #29 to think in detail about what support for a relational data model on Tesseract should look like.
In this function, I'm deleting a list as well as its associated cards (since the data is relational):
Maybe
Tesseract.remove
could take an array of indices as well as a single index?We were also talking about batch updates the other day, this would be a very good use case for them. I expect that I want my removal of the list and it's associated cards to all happen in one transaction as opposed to individual actions:
The text was updated successfully, but these errors were encountered: