Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on Optimising the "convert to comment" workflow

Post

Optimising the "convert to comment" workflow

+4
−0

I just handled some "not an answer" flags by converting an answer to a comment on another answer. The "convert to comment" dialog asks for a post ID. The obvious way to supply this was to copy a link to the target answer, then paste the link into the dialog and edit down to just the ID. To my surprise, pasting resulted in a floating point number (actual digits changed, but something like .123456123458e-123458). My guess is that because the input type is number the browser filtered against a regex.

I think the easiest way to optimise this workflow would be to have a "Post ID only" in the "copy link" options. Maybe it should only be visible to people with mod powers, unless there are other use cases where it would be helpful.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Or we could make "convert to comment" accept the post URL too (have the code extract the post ID inst... (6 comments)
Or we could make "convert to comment" accept the post URL too (have the code extract the post ID inst...
Monica Cellio‭ wrote about 2 months ago

Or we could make "convert to comment" accept the post URL too (have the code extract the post ID instead of having the human do it).

trichoplax‭ wrote about 2 months ago

Will the moderator always want to attach the comment to either the question or one of its other answers? If there is never a need to choose any other post, could the dialog list the question and its answers rather than taking an id? This could be in the form of a list of posts, each showing the author and a few lines from the start of the post (since some authors may post 2 answers, or a question and an answer).

Would this be helpful for moderators?

Peter Taylor‭ wrote about 2 months ago

Monica Cellio‭, that would also work. I considered suggesting it, but it seemed to have more potential for unintended consequences: although I don't know the Codidact code, my experience with other web frameworks suggests that it would mean changing from a built-in field validator to a custom one which would require maintenance.

Peter Taylor‭ wrote about 2 months ago

trichoplax‭, it seems likely that that would be the case, but I don't know that we have enough experience accumulated yet to rule out weirder use cases.

trichoplax‭ wrote about 2 months ago

Good point about unexpected use cases. When development time is available, I wonder if we could have multiple choice (the question and its answers) followed by the current post id approach as a fallback.

  • Question
  • Answer 1
  • Answer 2
  • Other - please enter post id
Monica Cellio‭ wrote about 2 months ago

I don't think we ever intended that you could turn a post into a comment on a completely different top-level post. Good point about needing extra validation if we accept the URL. The selector trichoplax‭ suggested sounds like a great usability improvement. I don't know how hard it is.

@Peter, in the meantime, you can do the cut/paste to extract the post ID from the "copy link" side instead of the tools side. I'm sorry for the extra hassle.