Open Bug 1953647 Opened 7 days ago Updated 7 days ago

[spike] Investigate improving linter tooling for Compose code

Categories

(Fenix :: Design System and Theming, task, P2)

All
Android
task

Tracking

(Not tracked)

People

(Reporter: 007, Unassigned)

References

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:

You need to log in before you can comment on or make changes to this bug.