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

[v6.0.4] double dispatch on all field changes #1771

Closed
bbenezech opened this issue Sep 15, 2016 · 5 comments
Closed

[v6.0.4] double dispatch on all field changes #1771

bbenezech opened this issue Sep 15, 2016 · 5 comments

Comments

@bbenezech
Copy link
Contributor

Can confirm it did not happen with 6.0.2 (checked twice)
@bbenezech
Copy link
Contributor Author

Can someone confirm/infirm? It looks like an environmental bug, but I can't figure why it would not happen on 6.0.2. :(

@bbenezech bbenezech changed the title [v6.0.4] double submit on all field changes [v6.0.4] double dispatch on all field changes Sep 15, 2016
@erikras
Copy link
Member

erikras commented Sep 15, 2016

Oh. I think I know.

erikras added a commit that referenced this issue Sep 15, 2016
@erikras
Fixed double change dispatch. #1771
b13de2b
@erikras erikras mentioned this issue Sep 15, 2016
Merged
erikras added a commit that referenced this issue Sep 15, 2016
@erikras
Fixed double change dispatch (#1772)
866c5d1 
* Fixed double change dispatch. #1771

* linting (again!)
@erikras
Copy link
Member

erikras commented Sep 15, 2016

Fixed in v6.0.5.

@bbenezech
Copy link
Contributor Author

Thx 💃

@lock
Copy link

lock bot commented Jun 2, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bbenezech @erikras