Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.3k
Fix wrong place of parent constructor call#9863
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Calling parent constructor after doing stuff in the overridedconstructor is a bad habit.
javiereguiluz left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I agree this is a better practice. Thanks!
yceruto commentedJun 1, 2018 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
In general Yes! but I guess it was on purpose for this case, becauseconsole commands call to |
Nek- commentedJun 5, 2018
|
Calling parent constructor after doing stuff in the overrided constructor is a bad habit. The documentation should encourage good practices.