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

changeDetection #142

Open
laurelnaiad opened this issue Feb 4, 2016 · 1 comment
Open

changeDetection #142

laurelnaiad opened this issue Feb 4, 2016 · 1 comment

Comments

@laurelnaiad
Copy link
Contributor

I did a search for "changeDetection" and didn't find anything, and I glanced at the the component.ts file and didn't see anything....

... so, has an thought been given to how/if to tackle changeDetection strategies beyond EventEmitter? Is this a matter of trying to port the router, or could something be done to create a facade here? Just wondering. Alternate changeDetection strategies would be really helpful in the immutable/flux/redux world.
@timkindberg
Copy link
Contributor

I'd say our top priority is syntax polyfilling. Your not going to get the semantic and perf benefits until you actually go to angular 2. So I'd think this might be lower priority but we we do want to polyfill the async pipe which is kind of related.

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
@timkindberg @laurelnaiad