From 2efa6030fd7ae5d86da97f09da4aa2077751f717 Mon Sep 17 00:00:00 2001 From: Shawn Pearce Date: Fri, 17 Jul 2015 13:33:22 -0700 Subject: [PATCH] Comment why followup action is hardcoded inside ActionJson Change-Id: I5fc116148cb4a8d361ae467a0016791db45dbc26 --- .../java/com/google/gerrit/server/change/ActionJson.java | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/gerrit-server/src/main/java/com/google/gerrit/server/change/ActionJson.java b/gerrit-server/src/main/java/com/google/gerrit/server/change/ActionJson.java index 023173ed09..fd20868db1 100644 --- a/gerrit-server/src/main/java/com/google/gerrit/server/change/ActionJson.java +++ b/gerrit-server/src/main/java/com/google/gerrit/server/change/ActionJson.java @@ -73,7 +73,10 @@ public class ActionJson { userProvider)) { out.put(d.getId(), new ActionInfo(d)); } - // TODO(sbeller): why do we need to treat followup specially here? + + // The followup action is a client-side only operation that does not + // have a server side handler. It must be manually registered into the + // resulting action map. if (ctl.getChange().getStatus().isOpen()) { UiAction.Description descr = new UiAction.Description(); PrivateInternals_UiActionDescription.setId(descr, "followup");