Method/Field sorting (a-z, grouped by visibility)
passsy opened this issue · comments
All methods and field of the AOSP source code are sorted alphabetically. This ends discussions about the "correct" order of functions. It also reduces merge conflicts because new methods/fields will be added at the correct place instead of the end of a class.
We improved this even further by grouping methods and fields by visibility. This means that public methods are sorted above protected, package private and private methods. Each group is sorted alphabetically. This moves implementation details to the bottom and public API to the top.
Our developer survey showed that our developers want to keep the method sorting. Especially the grouping by visibility, we use for years, is the favorite.
Already implemented