AutoValueImmutableFields
AutoValue recommends using immutable collections

Severity
WARNING

Alternate names: mutable

The problem

AutoValue instances should be deeply immutable. Therefore, we recommend using immutable types for fields. E.g., use ImmutableMap instead of Map, ImmutableSet instead of Set, etc.

Read more at:

Suppress violations by using @SuppressWarnings("AutoValueImmutableFields") on the relevant abstract getter.