Allow individual comments to be marked as draft#173305
Allow individual comments to be marked as draft#173305alexr00 merged 6 commits intomicrosoft:mainfrom
Conversation
20985e9 to
e63a47d
Compare
e63a47d to
51396e6
Compare
|
Any initial thoughts on the proposal, regarding naming or structure? |
|
@hermannloose I haven't had a chance to give this the review it deserves. I will plan to review it during our next iteration (starts in 1.5 weeks). |
This is a proposal for microsoft#171166.
51396e6 to
cc614c8
Compare
|
I dropped
No strong opinions on |
alexr00
left a comment
There was a problem hiding this comment.
With the visibility to state change I would accept a complete PR to add the published/draft feature.
alexr00
left a comment
There was a problem hiding this comment.
Thank you for the PR and for your patience with my slow review!
This is a proposal for #171166.
The names are rough suggestions, I am not sure if "visibility" is more descriptive than e.g.
CommentDraftState.CommentThread.hasDraftCommentsis included to show how we would conceptually want this to roll up into the thread. The surrounding features suggested in #171166 all operate on threads, buthasDraftCommentsdoes not necessarily need to become part of the API surface, it could be implicit and the relevant parts like line gutter decorations could just do the same iteration ad-hoc.Staying with the example of line gutter decorations for illustration, our ideal UX would be:
$(comment)$(comment-unresolved)$(comment-draft)Note that in this particular case for the UI, it ends up looking like the "draft" state is mutually exclusive with resolved or unresolved
CommentThreadState, but they are separate things, e.g. there could be two icons for lines that have a thread (or threads) with drafts, one icon to give the state, one icon to indicate presence of drafts.