Different labels for new discussions and replies #228
No reviewers
Labels
No labels
Component: User interface
Component: Wymeditor
Help wanted
Level: Difficult
Level: Easy
Level: Moderate
Pagetype: Festival
Pagetype: Mailinglist
Pagetype: Peer reviewed article
Pagetype: Text
Privacy GDPR AVG
status: has conflicts
Status: Needs changes
Status: Needs discussion
Status: Needs review
Status: Ready to merge
Status: Waiting for response
Type: Bug
Type: Enhancement
Type: Question
Usecase: De Stadsbron
Usecase: Koppelting
Usecase: MeetjeStad
Value: Coders
Value: Security
Value: Users
Value: Visitors
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
harmen/hypha!228
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "different-labels-for-comments-and-sub-comments-alternative"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
…comments.
Also fine with me to stick with the other version.
@ -1157,17 +1157,17 @@ EOF;* @return stringPlease leave away the
rowsandcolumnsand the<strong>in these statements, beter to instead give the fields a descriptive class, so styling can be adapted via hypha.css.Alternative:
<label for="$commentFieldName" class="comment-field-name-label"> $react </label><textarea name="$commentFieldName" id="$commentFieldName" class="comment-field-name"></textarea>@ -1157,17 +1157,17 @@ EOF;* @return stringThis is the subject of #217 and fixed by #219. I think it is out of scope for this PR, so I'm resolving this conversation.
I've rebased this PR, removed some code duplication and renamed the strings to
art-comment-on-articleandart-comment-on-commentto make it a bit clearer where they are used. I've also changed "Join the discussion" to "Join this discussion", the make it more clear that there are different discussions and you're replying to a particular one. With that, I think this is ready to merge.