Stefan Buhrmester
Stefan Buhrmester
Iv been trying to implement that but I'm n able to figure out I in th watcher _which_ field h changed. So I'm now doing a `collection.update(id, {$set: enitiredocument}` call....
I've been using the `collection-helpers` package to implement a `save` method on documents (example: https://github.com/buhrmi/q-editor/blob/master/lib/collections.coffee#L149). Then I added a watcher like this: watch: { myDocument: { deep: true, sync: true,...
Maybe you should try this really nice alternative https://github.com/MDSLKTR/pouch-vue ✌️
They're too busy Qurating the internet
Right. I'm just thinking about how to make common use cases easier to implement. Consider this (I think rather common case): - A search box and results are displayed on...
I wonder if it's possible to modify the SSR compiler to produce async code. So that the produced code actually executes all promises it encountered in `{#await}` blocks, and uses...
The entire render path would need to be async 🤷
Yes, I've seen that the remote node is checking for new events using `get_head`. However, in the "reference" implementation, a node actively notifies the randomly choose remote node about a...
Hmm. I can't see it. Where in the IPFS branch code is the local node notified?
If this is true then maybe there is something really counter-intuitive going on with Swirlds. Assuming I'm a local node and an event occurred (for example, a new transaction on...