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

Object observation tip from jdanyow and Rob #38

Closed
wshayes opened this issue Mar 26, 2016 · 3 comments
Closed

Object observation tip from jdanyow and Rob #38

wshayes opened this issue Mar 26, 2016 · 3 comments

Comments

@wshayes
Copy link

wshayes commented Mar 26, 2016

aurelia/framework#381 (comment)

@Vheissu
Copy link
Owner

Vheissu commented Mar 27, 2016

Something definitely worth adding into the object binding section. Thanks @wshayes

@wshayes
Copy link
Author

wshayes commented Mar 28, 2016

Rob also had this tidbit which helped me as well (from view it on GitHub aurelia/framework#367 (comment)):

However, my personal recommendation is to not put data access inside of "widgets" but instead to put that inside "screens" that are controlled by the router. Then you can control navigation if there is a failure. Those screens can then bind the data into the widgets which encapsulate some common rendering.

On Mar 27, 2016, at 7:57 PM, Dwayne Charrington notifications@github.com wrote:

Something definitely worth adding into the object binding section. Thanks @wshayes https://github.com/wshayes

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub #38 (comment)

@Vheissu
Copy link
Owner

Vheissu commented Mar 29, 2016

This made its way into the latest release and the binding chapter 6.

@Vheissu Vheissu closed this as completed Mar 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants