New user comment table on event page #271
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…d display user avatars
…s rather than putting the thread in the dom direct
…d display user avatars
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The old one ^ is naff:
I wanted to fix #269 and so took a pass at the whole table:
There are now 2 tables for resolved and unresolved comments, the unresolved starts off collapsed.
Because on old events there will be broken links (see #270) there will be threads that you cant link from, these are grouped into an automatically hidden section (No section found)
Comments are now grouped by the section they originated on (again collapsible) there are now links to the whole section and perhaps the most cool thing is that the thread itself can now be opened inside the event page and replied to/deleted/resolved. It is probable that you might get instant feedback on the deletion because I didn't do the instant mutation of the api call result since its a pain and this is buried well in the back of the site and probably will never be used.