-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Deprecate and remove function argument in Ember.assert/deprecate/etc #11898
Comments
I've attempted to partially resolve this issue in #11933. Would appreciate any advice for fully satisfying the issue and any problems with my PR. Thank you. |
@rwjblue, @stefanpenner is it still possible to create pr with deprecation or you will just remove this functionality? @mmun has written that it should be remove in beta 2.0. |
It's far too late for this, but we can do it now in preparation for Ember 3.0. |
In researching this, it looks like @kuzirashi has done a lot of great work moving this along in [https://github.com//pull/12370](PR 12370). I would love to help move this forward if it needs more work, or have it closed if Kuzirashi's work finished it. |
@kylemellander - Thanks for doing the research on this, I think this is closed! |
The following should throw a deprecation:
The message should be something like "Functional arguments are ambiguous with constructors. Please use
!!Constructor
for constructors, or an IIFE to compute the deprecation value. In a future version of Ember functions will be treated as truthy values instead of being executed."Needs to be deprecated in stable (1.13), removed in beta (2.0).
The text was updated successfully, but these errors were encountered: