« first day (132 days earlier)      last day (502 days later) » 

Anonymous
4:35 PM
@Downgoat You should now be part of the www-data group
 
7:51 PM
Do comments have markdown?
 
Anonymous
Yes
 
does that include like code-blocks (i.e. multi-line comments)
If that's the case we could do something like twitter-style comments where those don't show until you expand
 
Anonymous
It's just the same rendering for now
 
Anonymous
We can always change/restrict it
 
It would be pretty painful needing to scroll 3-VHs to get to the next answer though
 
7:57 PM
I like the way SE does comments (not when it comes to threading, but the way they show / hide them)
 
lemme make some mockups in pro-design software microsoft paint
 
Anonymous
@Downgoat That is both painful and relatable
 
how is this example
 
Anonymous
Decent
 
will we have comment votes?
how should we determine which comments to show
 
Anonymous
8:12 PM
Top-level comments only, max 5, with buttons to expand
 
Anonymous
And yes, comment votes, both up and down
 
@Mego are there backend for these already?
 
Anonymous
Don't think so, but it'll just be /vote/comment/<id>
 
ok, for now I'll just sort by date posted then
should it be newest or oldest first?
 
Anonymous
Oldest
 
8:15 PM
For a nested comment, is comment.post set or is it null?
 
Anonymous
Still set
 
Anonymous
It has comment.parent
 
so top level comment is SELECT TOP 5 FROM PostComment WHERE parent IS NULL ORDER BY date_created DESC
 
Anonymous
and post_id = <id>
 
would this work: answer.comments.order_by(AnswerComment.date_created.desc())
 
Anonymous
8:28 PM
I think so
 
8:51 PM
on a different topic, TIO integration is pretty weak rn, if anyone wants to draft how they could work better feel free to
 
9:28 PM
do we want to save comment drafts or is that too complex for too little benefit
 
Anonymous
Too much
 
>_< frontend-ing in JS is so painful
 

« first day (132 days earlier)      last day (502 days later) »