From 48118291d27cc16497b6d0314c0ea30430b4ba45 Mon Sep 17 00:00:00 2001 From: Oliver Byford Date: Fri, 19 Aug 2022 14:33:51 +0100 Subject: [PATCH] Remove unused gfm: true from marked config The documentation for the `pedantic` option [1] says: > If true, conform to the original markdown.pl as much as possible. Don't fix original markdown bugs or behavior. Turns off and overrides gfm. Verified that this option is doing nothing by comparing the build output with and without this setting, and there is no difference (other than the obfuscated email address on the community page, which is non-deterministic and so changes with every build): ``` $ diff -r deploy/public-marked-main deploy/public diff -r deploy/public-marked-main/community/design-system-working-group/index.html deploy/public/community/design-system-working-group/index.html 1045c1045 <

In the meantime, if you are interested in joining the working group email the Design System team at govuk-design-system-support@digital.cabinet-office.gov.uk.

--- >

In the meantime, if you are interested in joining the working group email the Design System team at govuk-design-system-support@digital.cabinet-office.gov.uk.

``` [1]: https://marked.js.org/using_advanced#options --- lib/metalsmith.js | 1 - 1 file changed, 1 deletion(-) diff --git a/lib/metalsmith.js b/lib/metalsmith.js index 6dc9fc3a14..83a8675ce9 100644 --- a/lib/metalsmith.js +++ b/lib/metalsmith.js @@ -230,7 +230,6 @@ module.exports = metalsmith(__dirname) // __dirname defined by node.js: name of // Markdown engine options smartypants: true, // use "smart" typographic punctuation - gfm: true, pedantic: true, highlight: highlighter }