-
Notifications
You must be signed in to change notification settings - Fork 235
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
chore: enable strict #631
chore: enable strict #631
Conversation
tsconfig.json
Outdated
@@ -8,6 +8,8 @@ | |||
"noLib": false, | |||
"outDir": "./dist", | |||
"removeComments": true, | |||
"strict": true, | |||
"strictPropertyInitialization": false, |
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.
@rkirov does it work for you if we disable strictPropertyInitialization
?
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.
@mgechev There are only few some places that forced me to disable this. I can enable this and initialize properties properly or even use a !
to indicate that I want hack that property. Let me know what should I do.
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.
If the job isn't too hard, I would prefer to use the default value of strictPropertyInitialization
. Could you update this PR in this direction ?
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.
@wKoza Updated.
@rafaelss95 great job! LGTM, I'll let @wKoza to have a look as well. |
Thanks, @mgechev :) |
Ping @wKoza. |
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.
LGTM @rafaelss95
Closes #629.