You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This causes an error when calling service methods on the server without a callback (because Rubberduck expects the last argument to be a callback) as described in feathersjs-ecosystem/feathers-memory#8.
The text was updated successfully, but these errors were encountered:
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue with a link to this issue for related bugs.
lockbot
locked as resolved and limited conversation to collaborators
Feb 8, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The reason is that the event mixins get initialized in setup (see https://github.com/feathersjs/feathers/blob/master/lib/mixins/event.js#L19) after the normalizer ran. I can't remember if there was a reason why this is running when overwriting setup instead of setting it up right away.
This causes an error when calling service methods on the server without a callback (because Rubberduck expects the last argument to be a callback) as described in feathersjs-ecosystem/feathers-memory#8.
The text was updated successfully, but these errors were encountered: