Allow replies to comments in annotations. #16
Labels
Comments
|
Original comment by Julian Kniephoff (Bitbucket: JulianKniephoff, GitHub: JulianKniephoff): Note to self: Remember to update the print view, once this is implemented. See also #28. |
|
Original comment by Julian Kniephoff (Bitbucket: JulianKniephoff, GitHub: JulianKniephoff): Resolved by pull request #16 |
JulianKniephoff
added a commit
to JulianKniephoff/annotation-tool
that referenced
this issue
Jan 10, 2018
…equest opencast#16) Some initial harmless grunt work
mliradelc
added a commit
to mliradelc/annotation-tool
that referenced
this issue
Jun 24, 2019
# This is the 1st commit message: Add HLS support Update files from develop branch Fixed German translation file syntax Closes opencast#173. Add Emacs configuration `npm update && npm audit fix` Changed `less` plugin for `grunt` This switches from `assemble-less` to `grunt-contrib-less` and updates the latter at least a bit, all in order to get rid of a few security vulnerabilities. Further updates pending mostly because of incompatibilities. Updated `grunt-contrib-less` to the latest version More package updates # This is the commit message #2: Removed unused grunt plugin # This is the commit message #3: Removed some unused dependencies # This is the commit message #4: Improved code quality # This is the commit message #5: Removed some dead code and obsolete comments # This is the commit message #6: Got rid of `box-sizing`-'polyfill" Box sizing has good enough support now. If we still want backwards compat, I feel like a CSS postprocessor would be a better approach. # This is the commit message opencast#7: Simplified some event handling code # This is the commit message opencast#8: Refactored comment model slightly Comments should be creatable without text. But I **do** see the problem this brings. So why not make the empty string the default text? ;) # This is the commit message opencast#9: Refactored some view cleanup and deleted related dead code # This is the commit message opencast#10: Allowed editing multiple annotations simultaneously # This is the commit message opencast#11: Use `maven-enforcer-plugin` instead of `prerequisites` Fixes opencast#187. # This is the commit message opencast#12: Pinned `maven-install-plugin` Fixes opencast#185. # This is the commit message opencast#13: Added an `npm start` script # This is the commit message opencast#14: Updated `grunt-cli` # This is the commit message opencast#15: Improved code quality # This is the commit message opencast#16: Revert back to a stable version of `grunt-cli` Closes opencast#188. # This is the commit message opencast#17: Fix XACML parsing of rules OAT filters for ACL rules with the wrong tag name "rules" instead of "Rule". # This is the commit message opencast#18: Fix exception during export when no e-mail is set # This is the commit message opencast#19: Simplified some of the export functions a bit # This is the commit message opencast#20: Remove unused and vulnerable dependency # This is the commit message opencast#21: Updated demo link in the README Changed the README to include a link to a working demo # This is the commit message opencast#22: Update README.md # This is the commit message opencast#23: Update checkstyle to fix a vulnerability # This is the commit message opencast#24: Improve the style of the checkstyle configuration # This is the commit message opencast#25: Update `grunt`
JulianKniephoff
added a commit
that referenced
this issue
Dec 4, 2019
…equest #16) Some initial harmless grunt work
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)
Users should be able to reply to a comment.
Optionally it might be an option to have a reply to a reply too.
The text was updated successfully, but these errors were encountered: