-
Notifications
You must be signed in to change notification settings - Fork 97
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
fix(lints) : non_constant_identifier_names #195
Conversation
c03d11d
to
9b10f65
Compare
Pull Request Test Coverage Report for Build 1928899728
💛 - Coveralls |
@@ -50,7 +50,7 @@ class _AboutViewState extends State<AboutView> { | |||
} | |||
|
|||
Widget _buildContributorsList() { | |||
switch (_model.stateFor(_model.FETCH_CONTRIBUTORS)) { | |||
switch (_model.stateFor(_model.fetchCONTRIBUTORS)) { |
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.
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.
So you mean to say these changes be reverted back and the lint for non_constant_identifier_names
be kept 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.
Check if you can avoid renaming the variables while supporting the rule.
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'm not quite sure what you meant here😅. Do I have to revert the changes? Or add ignore statements at a few places?
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.
We want to keep using UPPER_CASE for the current variables we have and while supporting non_constant_identifier_names
.
You need make UPPER_CASE variables as const
and keep them in UPPER_CASE. In this way the rule will not be causing issue since we made it a constant.
@manjotsidhu Please chalk out the required changes that you want here. |
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.
You need to mark all the UPPER_CASE variables as const
. In this way the rule will not be causing issue since we made it a constant.
Refer #149
Fixed lints for the rule - non_constant_identifier_names