Help Improve Our Codebase by Fixing Linter Warnings!

[TimoPtr]

We've recently enforced new linting rules to enhance code quality and maintain consistency across our project. To prevent an overwhelming number of changes in a single pull request (PR), we've added the current warnings to baseline files.

We invite you to help us improve the codebase by addressing these linter issues! This is a fantastic opportunity to get familiar with the codebase and contribute to the project.

Guidelines:

• Check out our Linter Documentation to understand the lint rules and how to run them.

• Scope Your Work:

  • No need to fix all issues—we prefer manageable PRs over giant ones.
  • Focus on fixing linter warnings within a specific Kotlin package.

• Submitting Pull Requests:

  • Don't create a separate PR for each issue.
  • Do group related fixes together in a single PR.

• Some issues in the :automotive Gradle module may not be relevant due to its dependency on :app we recommend you to Ignore linter issues from :automotive for now.

• You can find the lint-baseline.xml file in each Gradle module directory.

We appreciate your help and look forward to your contributions!

If you have questions or need assistance, check our documentation.