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 »
Meta

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on "Review suggested edit" page doesn't display Markdown source correctly

Parent

"Review suggested edit" page doesn't display Markdown source correctly

+6
−0

I recently suggested an edit to an answer.

Basically, I formatted some code, adding code fences around it:

suggest edit - editor shows newlines

But at the "Review suggested edit" page, the differences are not clearly displayed.

It shows all the answer text in a single "line":

pending edit - no newlines

Hence, it's not only unclear what changes were made, but it also doesn't show the correct Markdown source (ex: there's a blank line before the code fences, but it's all displayed as it was in the same line).


Another case: someone suggested an edit to my question, but I can't see what was changed.

I had to copy-paste the text to an external editor and perform the diff myself to see that a single character was changed (a typo was fixed). Just looking at the page, it was really hard to find the difference:

hard to find diff

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

General comments (4 comments)
Post
+4
−0

While reviewing older bug reports we discovered that the first problem is now working; the code fences show up in the diff. The second one still shows as one line without a clear diff, but I don't think we've seen a recent case so it's possible that's a one-off data error of some sort. I'm going to mark this as status-completed; if you see the problem again, please let us know with a new post. And I'm sorry this sat so long without a proper response. (For tracking purposes: GitHub issue.)

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

1 comment thread

Regarding the second case, there's an example [here](https://software.codidact.com/posts/284597/histo... (3 comments)
Regarding the second case, there's an example [here](https://software.codidact.com/posts/284597/histo...
hkotsubo‭ wrote over 2 years ago

Regarding the second case, there's an example here: in edit #6, only one character was removed, and there's a strikethrough showing that. It's still hard to find because it's only one single char in a long post, but I guess we can consider this issue fixed. Thanks!

Monica Cellio‭ wrote over 2 years ago

The strikethrough on 'd'? Yeah, that's hard to see, though fortunately, the diff highlights the line that changed so it's not as bad as when the highlighting didn't show up and you had to scan the whole diff. Do you have thoughts on a better way to show one-character differences? How could we make that easier to find?

hkotsubo‭ wrote over 2 years ago · edited over 2 years ago

"The strikethrough on 'd'?"

Yes!

One idea to make it easier to find: the line that was changed has a different highlighting, which means the system already knows that the difference is on that specific line. Maybe it could show only that line (or have an option to toggle between "show all" and "show only lines that differ"). But that's a different request and should be made in another post, I guess (not with time to do it now, though).