While porting code to TypeScript I came across a situation where a cached set operation on the root node (db.root.set(...)) would not sync to the server, and quite possibly cause an exception too. Fixing this is the next release, which will be entirely TypeScript.
While porting code to TypeScript I came across a situation where a cached
setoperation on the root node (db.root.set(...)) would not sync to the server, and quite possibly cause an exception too. Fixing this is the next release, which will be entirely TypeScript.