opendev/gerrit
Code Issues Proposed changes

Implement NoteDB portion of resolvablility

Browse Source 
The server doesn't need to handle resolvedness of a thread; the plan is
for it to be an entirely client-side implementation. Whatever value the
most recent comment has for 'unresolved' is the value that will
determine whether the thread is resolved, but each individual comment
will still have that value populated so as to keep a log of when it was
changed and who it was changed by.

Change-Id: If45057935f4f30bb6babbe5e80223b8da3fa694f
This commit is contained in:
Kasper Nilsson
2016-12-13 12:27:31 -08:00
parent b148a81817
commit c101b42cc3
11 changed files with 185 additions and 61 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
gerrit-extension-api/src/main/java/com/google/gerrit/extensions/client/Comment.java
View File

@@ -34,6 +34,7 @@ public abstract class Comment {
public String inReplyTo;
public Timestamp updated;
public String message;
public boolean unresolved;
public static class Range {
public int startLine;
@@ -101,7 +102,8 @@ public abstract class Comment {
&& Objects.equals(range, c.range)
&& Objects.equals(inReplyTo, c.inReplyTo)
&& Objects.equals(updated, c.updated)
&& Objects.equals(message, c.message);
&& Objects.equals(message, c.message)
&& Objects.equals(unresolved, c.unresolved);
}
return false;
}