Abandon: Remove unnecessary null check in updateChange
Callers can assume that ctx.getChange will not return null. Change-Id: Id01318d9f71188770e26e76ca9775da9a9d0ae19
This commit is contained in:
@@ -123,7 +123,7 @@ public class Abandon implements RestModifyView<ChangeResource, AbandonInput>,
|
||||
change = ctx.getChange();
|
||||
PatchSet.Id psId = change.currentPatchSetId();
|
||||
ChangeUpdate update = ctx.getUpdate(psId);
|
||||
if (change == null || !change.getStatus().isOpen()) {
|
||||
if (!change.getStatus().isOpen()) {
|
||||
throw new ResourceConflictException("change is " + status(change));
|
||||
} else if (change.getStatus() == Change.Status.DRAFT) {
|
||||
throw new ResourceConflictException(
|
||||
|
||||
Reference in New Issue
Block a user