Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Setting a computed attribute triggers two change events #140

Open
emileber opened this issue Jul 7, 2016 · 1 comment
Open

Setting a computed attribute triggers two change events #140

emileber opened this issue Jul 7, 2016 · 1 comment

Comments

@emileber
Copy link

emileber commented Jul 7, 2016

Related to the line 486, if I set a computed attribute, the following events are triggered:

  • change:myField change with (model, value) from epoxy,
  • standard backbone change with (model, options)

This has the side-effect of calling every listeners of the change event for this model twice, and with the wrong params the first time.

I don't get when this would be necessary (and a good idea)? Am I missing something?
@jekuno
Copy link

jekuno commented Jul 8, 2016

Please also have a look at #138 regarding this issue.

@emileber emileber mentioned this issue Jul 8, 2016
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@emileber @jekuno