Open Bug 1953647 Opened 11 months ago Updated 2 months ago

[spike] Investigate improving linter tooling for Compose code

Categories

(Firefox for Android :: Tooling, task, P2)

Product:
Firefox for Android
Component:
Tooling
Platform:
All
Android
Type:
task

Tracking

()

People

(Reporter: 007, Unassigned)

References

(Blocks 1 open bug,
URL
)

Details

(Whiteboard: [fxdroid][group4])

To improve upon our existing linter, we should have some rules specifically for Compose code with the goals of:

  • Having separate code styling rules where applicable (e.g. function parameter length).
  • Preventing the use of direct Photon colors
  • Enforcing the usage of Acorn tokens
  • Promoting state hoisting
  • Avoiding unstable collections
  • Promoting general Compose best practices and those agreed upon by the team

As part of this ticket, investigate adding lint rules to meet these goals.

Starting point:

Moving this to the Tooling component since that would probably be more appropriate.

Component: Design System and Theming → Tooling
Blocks: compose-lint
No longer blocks: detekt/ktlint
You need to log in before you can comment on or make changes to this bug.