-
-
Notifications
You must be signed in to change notification settings - Fork 431
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
Lint the Code Base - Top Priority #691
Comments
If possible, can I work on this issue? |
I already opened this issue, but still my PR is on hold. |
@Neha62-lit Would Pedantic create a differences in the output when compared to the approach we are using? |
Closed
Merged
@sumitra19jha Use this issue to lint the develop branch. Use this method to automatically close the issue when the PR is completed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We were having a large number of issues with code conflicts due to unlinted code. We have now added automated linting to the PR process, but will need to lint the entire codebase to this new standard.
Linting will include following the steps in the automation script shown here. Specifically:
flutter format
command on the code baseflutter format --set-exit-if-changed .
Coordinate with @DeltaHarbinger and @Sagar2366 on this issue.
We will reopen PRs when this issue is resolved. We are looking for someone to work on this quickly.
The text was updated successfully, but these errors were encountered: