-
-
Notifications
You must be signed in to change notification settings - Fork 752
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Uberproto objects don't need to be extended #57
Comments
Actually nevermind. We probably do always want to create a new object it might be weird to get behaviour mixed into your existing object. |
daffl
added a commit
that referenced
this issue
Aug 19, 2018
* Rename repository and add to npm scope * Remove circular Feathers dependency
daffl
added a commit
that referenced
this issue
Aug 21, 2018
* Rename repository and add to npm scope * Remove circular Feathers dependency
daffl
pushed a commit
that referenced
this issue
Aug 21, 2018
daffl
pushed a commit
that referenced
this issue
Aug 22, 2018
daffl
pushed a commit
that referenced
this issue
Aug 28, 2018
daffl
pushed a commit
that referenced
this issue
Aug 28, 2018
daffl
pushed a commit
that referenced
this issue
Aug 29, 2018
daffl
pushed a commit
that referenced
this issue
Aug 29, 2018
daffl
pushed a commit
that referenced
this issue
Aug 29, 2018
daffl
pushed a commit
that referenced
this issue
Aug 29, 2018
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. |
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
By default all services will be extended with Uberproto in https://github.com/feathersjs/feathers/blob/master/lib/application.js#L22. While this most likely works it isn't necessary if the object is already an
instanceof Proto
.The text was updated successfully, but these errors were encountered: