The Material Components contributing policies and procedures can be found in the main Material Components documentation repository’s contributing page.
The Android team also abides by the following policy items.
Since we all want to spend more time coding and less time fiddling with whitespace, Material Components for Android uses code conventions and styles to encourage consistency. Code with a consistent style is easier (and less error-prone!) to review, maintain, and understand.
If the style guide is not explicit about a particular situation, the cardinal rule is to be consistent. For example, take a look at the surrounding code and follow its lead, or look for similar cases elsewhere in the codebase.
TODO: Add general conventions
We provide configurations for Android Studio that allow for auto-formatting to the below guidelines. Java style is also enforced via checkstyle as part of our Gradle build.
TODO: Link to IDE presets
We follow the Google Java Style Guide.
- 2 space indentation
- Resource naming (including IDs) is
lowercase_with_underscores - Attribute ordering:
xmlns:android- other
xmlns: android:idstyleandroid:layout_attributesandroid:paddingattributes- other
android:attributes app:attributestool:attributes