Open maitrid opened 7 years ago
Ah... yes. The transactions package writes to top-level fields on the document:transaction_id
(always) and, for soft deletes only, deleted
.
I'm guessing you're editing a field in a sub-document, which means that whole re-render doesn't normally need to happen. Is that the case?
Yes, that's exactly what i'm doing. Thanks!
In an app using Meteor + React that updates couple of documents after the user submits a form, under normal circumstances, only the relevant component updates, but after implementing tx.start, and tx.commit around the data update calls, the whole page re-renders after form submit. Is there anything that can prevent the whole page re-rendering?