commit 699516107aa05467c9811fb8b4bdadb5fca5f278
author Dhruv Srivastava <dhruvsri@google.com> Mon Dec 07 21:37:03 2020 +0100
committer Dhruv Srivastava <dhruvsri@google.com> Fri Jan 08 12:19:31 2021 +0100
tree 8dd2ea09fe1090692803ded4bbff3584fb725aa2
parent b4c32b2b5ca7a981446ac0db18c31c6462755f36

Update thread in file view if user updates it in other places

Currently user can interact with the comment threads in the change
view through:
1. reply dialog
2. change log
3. comments tab
4. individually expanded diff in file list

When user creates or updates a draft in views 1,2 or 3 they send
an event to change-view(comment-refresh) which requests new drafts
and updates the ChangeComments object.
The comment threads in diffs are however not updated if they were
already expanded.
This leads to inconsistent state where the thread is updated in
one view but not in another view.
This inconsistency also leads to other inconsistent states such as
creating two different drafts on the same thread in two different
views. (https://imgur.com/a/ul1X23P)

gr-file-list already has the method reloadCommentsForThreadWithRootId
which updates a thread with given rootId if it's updated in other
places.

gr-file-list does not render the gr-thread-list element, therefore
changing the comment thread in file view itself does not fire the
thread-list-modified event and cause re-rendering of the thread.

Change-Id: I77f5fea9083f75a11aa3ffc1530e3e061d74aa75