Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 17
    Your understanding is perfectly correct. In the revision history we calculate and diff a post's HTML on the fly based on the revision's markdown source. That means that after switching over to CommonMark, even revisions that predate the CommonMark migration will be rendered with the new CommonMark renderer. I know, that's less than stellar but it's all we can do if we don't want to keep the old renderer around forever. Commented Jun 2, 2020 at 8:40
  • 1
    @HamVocke - perhaps, once the switcheroo has been performed on all the sites, and everything that can go wrong has gone wrong (and subsequently been fixed) - consider running the updated migrator script on the earlier post revisions? Commented Jun 3, 2020 at 5:52
  • 8
    @Robotnik I think that would make it impossible to audit the changes. While the current way of updating simply makes a new revision, what you suggest will change the revisions themselves, leaving nothing to compare them with. That'd be awful IMO. Commented Jun 3, 2020 at 18:20
  • 2
    @HamVocke "That means that after switching over to CommonMark, even revisions that predate the CommonMark migration will be rendered with the new CommonMark renderer." In that case, please consider open-sourcing the client-side renderer so that it can be turned into an add-on/userscript for viewing old revisions. Commented Jun 4, 2020 at 11:39
  • 3
    @kelvin you can find the source code for our old client-side markdown renderer on GitHub. Note that the published version is missing the latest significant feature addition, which is the ability to handle nested code blocks. I hope this can be helpful nevertheless. Commented Jun 4, 2020 at 12:26