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

Observe#on #394

Closed
rxaviers opened this Issue May 24, 2013 · 3 comments

Comments

Projects
None yet
3 participants
@rxaviers

Have you considered a .on() alias for .bind()?

@matthewp

This comment has been minimized.

Show comment
Hide comment
@matthewp

matthewp May 31, 2013

Contributor

To me on signifies that I'm working with an EventEmitter type of object, and that's not really what an Observe is. on("change", ... makes sense but does on("somePropertyName", ... ? Not sure.

Contributor

matthewp commented May 31, 2013

To me on signifies that I'm working with an EventEmitter type of object, and that's not really what an Observe is. on("change", ... makes sense but does on("somePropertyName", ... ? Not sure.

@imjoshdean

This comment has been minimized.

Show comment
Hide comment
@imjoshdean

imjoshdean Sep 27, 2013

Contributor

Honestly, I don't see the harm in aliasing can.on/off for can.bind/unbind. Looking at on("change", ... vs on("somePropertyName", ... they are both listening for emitted events, just different names.

Contributor

imjoshdean commented Sep 27, 2013

Honestly, I don't see the harm in aliasing can.on/off for can.bind/unbind. Looking at on("change", ... vs on("somePropertyName", ... they are both listening for emitted events, just different names.

@rxaviers

This comment has been minimized.

Show comment
Hide comment
@rxaviers

rxaviers Oct 9, 2013

👍 cool

rxaviers commented Oct 9, 2013

👍 cool

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment