Closed vanhumbeecka closed 9 years ago
Yeah... this was originally a package to expose a client-side undo-redo stack that is user specific, hence the need for the user.
Putting
tx.requireUser = false;
in a file that's common to both client and server should fix things up.
The next release is majorly refactored and focuses more purely on implementing app level transactions. The undo-redo stuff will be split out to a separate package.
Ok, thanks for clearing that up.
"User must be logged in to start a transaction." I get this "warning message" when executing a transaction in a method on the server. In my transaction, I create a user along with some other samples, so no user can be logged in at that moment.
Why is it necessary to have a user logged in, when trying to execute a transaction? I don't see the point.