Local Collection Accepting Mutations
Hi - I noticed the section in the documentation where it's called out that LocalOnly and LocalStorage collections require extra calls to acceptMutations. I'm working on a custom collection, and I had a couple quick questions about this to make sure I'm avoiding this behavior:
1. I assume this is due to the lack of the immediate: true flag in the begin() function?
2. Why is this the case? Is it just so you can have combined local/server transactions and then deliberately allow the divergent local state behavior, I guess? Or is there some other reason I'm not understanding?
1. I assume this is due to the lack of the immediate: true flag in the begin() function?
2. Why is this the case? Is it just so you can have combined local/server transactions and then deliberately allow the divergent local state behavior, I guess? Or is there some other reason I'm not understanding?
