Presence of virtualFields causes fields with autoValues not to be created about meteor-collection2 HOT 8 CLOSED

@crsssl, thanks for pointing this out. I can replicate, and from what I can tell, it's actually due to this issue with Meteor. Autovalues are added by C2 in deny functions and virtual fields are added by transforms. Due to the Meteor issue, autovalues won't work if you specify a transform, which includes using virtual fields.

The good news is that the fix to this was merged into Meteor devel branch today, so the next Meteor release will have it.

from meteor-collection2.

That is good news. Thanks for this.

from meteor-collection2.

@crsssl, based on my test, this seems to be working now in Meteor 0.7.0. Let me know if you find otherwise.

from meteor-collection2.

Confirmed. Seems to be working.

from meteor-collection2.

Hi Eric.
I was wondering if $addtoset and $pull operators were now supported as
well. (I seem to recall they weren't when we last discussed this.) If not,
are these on your timeline?
Thanks.

On Tue, Dec 17, 2013 at 6:24 PM, Eric Dobbertin [email protected]:

@crsssl https://github.com/crsssl, based on my test, this seems to be
working now in Meteor 0.7.0. Let me know if you find otherwise.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/29#issuecomment-30802166
.

from meteor-collection2.

Supported by autoValue? Or just in general?

As far as I know, all operators are validated correctly by SimpleSchema. There are a few validations that SimpleSchema can't do, like testing min/max for $inc, but those will hopefully be validated by collection2 eventually.

from meteor-collection2.

In general. Yeah, I'm not sure which project it was referring to. (I had a bunch of //TODO: when $addtoset and $pull are supported comments littering my code, so this reminded me of the issue.

from meteor-collection2.

All tested and it looks like there isn't an issue. Probably the way I was coding it up.
Thanks again for the input.

from meteor-collection2.