-
-
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
init
in classic components takes an argument in the stable types
#20483
Comments
Whoops, this one is quite straightforward and I missed it while doing the work for 5.1.1. Should be fixed by #20492. |
Thanks for the release! However, even with 5.1.2 I get the same error. The
So I'm not sure whether we really need to pass |
I pushed another commit to the reproduction repo. It simply does: import Controller from '@ember/controller';
export default class ApplicationController extends Controller {
public override init(): void {
super.init();
}
} That causes an error. That is,
|
Will take a gander sometime this week or next to try to get this resolved. Thanks for the follow-up! |
init
in classic components takes an argument in the stable typesinit
in classic components takes an argument in the stable types
🐞 Describe the Bug
init
in classic components used to not accept any arguments andsuper.init()
could be called like that. Since 5.1.0, this no longer works. I believe this is a bug.🔬 Minimal Reproduction
Repo.
Run
npm install
and then./node_modules/.bin/tsc
.😕 Actual Behavior
Type error on
super.init()
.🤔 Expected Behavior
No error. Removing the last commit (which upgrades Ember) and rerunning
npm install
and thentsc
will remove the errors.🌍 Environment
cc @chriskrycho
The text was updated successfully, but these errors were encountered: