Naming

Naming

A list of naming conventions used throughout PRIVVY:

Classes

• Different PRIVVY Component class names need to include which PRIVVY element they are (eg. ButtonPresenter, NumberViewModel, etc.). An exception is the View element, as these can be named '[name]Fragment' or '[name]Activity'
• etc.

Methods

• Methods in each PRIVVY Contract should be named the same name if they are a part of the same up vs. down stream, and are only used to delegate.
• etc.

Fields

• etc.

Dagger ?

• etc.