Welcome to Codidact Meta!
Codidact Meta is the "town hall" (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.
Show revisions both in source, and rendered.
My Rationale
When I posted comments/thread/11196#comment-27732, I wanted to link to a rendered version of the revision, in order to demonstrate the new version of the post.
Certainly, I could just inform the user to view the current revision, but that might change between me posting my comment, and them viewing it. (Who doesn't deal with some notifications a few months late?)
More generically, when viewing a revision, not needing to paste it into an external Markdown renderer is convenient. I can't provide examples anymore, but I know that I've wanted it a few times.
If none of that convinces you:
-
Stack Exchange provides this! 😊
-
This would mitigate
posts/294861.
(Lack Of) Duplicates
posts/search?search=render+history returned 0 relevant results at ⪅ +2025-10-30T00:05:27+00:00.
The Applicable Version
Version
b7103551(2025-10-17 15:42:56Z)
1 answer
I just ran into another reason for this, which is when reviewing edits. An edit was proposed that seemed like it was fixing something with images, or putting them in-line. I couldn't see what the result would be.
In this case I approved the edit because the user had been around for a while and seemed generally trustworthy (of course that means he should have been able to make edits directly. Codidact is way too tight with abilities, but that's for another discussion). Fortunately, the result looked good, and I didn't have to roll it back. If the user wasn't as known to me, I might have rejected the edit because I couldn't tell what I was approving.
0 comment threads
1 comment thread