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.

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

In-place data changes lead to non-reactivity in route data context #23

Open
tmeasday opened this issue Jun 17, 2014 · 1 comment
Open

Comments

@tmeasday
Copy link
Contributor

See iron-meteor/iron-router#667

Reproduction: https://github.com:tmeasday/IR693

The issue is due to https://github.com/EventedMind/blaze-layout/blob/master/layout.js#L144

@tmeasday
Copy link
Contributor Author

@cmather - I foolishly didn't record what we decided here. Was it that we'd make setData take a copy to compare with?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant