-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
db.observe using {fields: {...}} doesn't function as it should #6
Comments
So, if you include Another Bad Solution
One should definitely be able to scope the reactivity as I have shown by using In these docs:
The query |
I can't think of a good solution to this problem ( without digging into your source ) other than observing the entire query and then manually applying a diffing layer before The main point is that the version number captures changes in the entire document, which is useless if I only care about changes in a slice of the document.I've been working on this library, but it's nowhere near complete. It tries to do things the Meteor way with scoping: data store which allows for scoped reactivity it'll work for the basics, but it's not anywhere close to ready. |
<EDIT: Read this first
I can't think of a good solution to this problem ( without digging into your source ) other than observing the entire query and then manually applying a diffing layer before setState is reached.
The main point is that the version number captures changes in the entire document, which is useless if I only care about changes in a slice of the document.
I've been working on this library, but it's nowhere near complete. It tries to do things the Meteor way with scoping: data store which allows for scoped reactivity it'll work for the basics, but it's not anywhere close to ready.
/EDIT>
Possible design flaw?
Problem:
Bad Solution, not even a solution:
Unhappy fix:
Worse Solution, not even a solution:
Unhappy hack:
Should this work?
This should not be necessary if specifying
fields
just worked.This doesn't work, nevertheless, but perhaps it should?
This forces us to write our own diffing code. I thought this library took care of that! Is there a bug somewhere, perhaps, or did I misinterpret the goal of this library? Thanks.
The text was updated successfully, but these errors were encountered: