-
Notifications
You must be signed in to change notification settings - Fork 6
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
Removing controller.isDirty default logic #10
Milestone
Comments
Was reading on my phone, didn't mean to close :). Is your concern that controllers are going away? |
Yep! |
I'm down to move this responsibility to the route, unless you have some other ideas. |
Sounds great - I'll update the title. |
blimmer
added a commit
that referenced
this issue
May 15, 2016
By default, we will check if the current route model hasDirtyAttributes. Resolves #10.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To be good Ember community members, we should discourage the use of
Ember.Controller
.It would be a breaking change, but perhaps we should guide users to provide their own
canUnload
or have logic that utilizesthis.modelFor(this.routeName)
instead.The text was updated successfully, but these errors were encountered: