ConfigUpdatedEvent: Use immutable type in field declaration
Error Prone reports [1] that a field initialized to hold an immutable collection should be declared using the immutable type itself. [1] https://errorprone.info/bugpattern/MutableConstantField Change-Id: I8058a45ad1c757671168ff237cecdedad04e8760
This commit is contained in:
parent
20fa6bd8b2
commit
7738f98c29
@ -37,7 +37,7 @@ import org.eclipse.jgit.lib.Config;
|
||||
* (+ various overloaded versions of these)
|
||||
*/
|
||||
public class ConfigUpdatedEvent {
|
||||
public static final Multimap<UpdateResult, ConfigUpdateEntry> NO_UPDATES =
|
||||
public static final ImmutableMultimap<UpdateResult, ConfigUpdateEntry> NO_UPDATES =
|
||||
new ImmutableMultimap.Builder<UpdateResult, ConfigUpdateEntry>().build();
|
||||
private final Config oldConfig;
|
||||
private final Config newConfig;
|
||||
|
Loading…
Reference in New Issue
Block a user