Skip to main content

Timeline for answer to We're switching to CommonMark by Eliah Kagan

Current License: CC BY-SA 4.0

Post Revisions

7 events
when toggle format what by license comment
Jun 4, 2020 at 12:26 comment added Ham Vocke StaffMod @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.
Jun 4, 2020 at 11:39 comment added kelvin @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.
Jun 3, 2020 at 18:20 comment added Ruslan @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.
Jun 3, 2020 at 5:52 comment added Robotnik @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?
Jun 2, 2020 at 8:40 comment added Ham Vocke StaffMod 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.
Jun 2, 2020 at 5:06 history edited Eliah Kagan CC BY-SA 4.0
grammar fix
Jun 2, 2020 at 3:17 history answered Eliah Kagan CC BY-SA 4.0