Open DaxChen opened 8 years ago
Looks like a load order issue. See https://github.com/matb33/meteor-collection-hooks/issues/153
Unfortunately, changing the order of the dependencies inside my package doesn't fix this. Anyone have another workaround? Not being able to use collection-hooks and collection2 together in Meteor methods would lead to a pretty significant setback in the app I'm working on.
@ryanfields did you figure this out?
@huevoncito it's definitely not a load order
@yogiben Nope. I've stopped using collection-hooks. I didn't really find any good alternatives though. I just do what I can to work around the need for hooks now.
Looks like schemas/hooks order is inverted between client and server side: #154.
This issue is still a thing, any updates?
Hi, @matb33
Here's a repo to reproduce the error
When inserting inside meteor method, only client side runs the before.insert hook before collection2 's schema check. Server side won't run the hook, and fails the schema check. Error message:
Am I doing something wrong? Or is this a bug?
Thanks! YuHuaiChen