You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This maybe more of a question/discussion instead of an issue.
Should we also include the usage of fenced code blocks (i.e. triple backticks ```) in the formatting chapter ?
Also I don't understand what would the
~~~
# my code here
~~~
{: .language-* }
method have over the ``` method?
Is there some additional functionality that it brings ?
The text was updated successfully, but these errors were encountered:
I believe the reason was that the Jekyll-based lessons all use kramdown syntax, and at the time the lesson was written, getting the backtick syntax would have required extra configuration (even though that syntax works now). I have a feeling that it was never updated because a) the official documentation never noted the change and b) the lessons would have retained the old syntax, which would have lead to a disconnect between contributors reading the documentation and the presentation of the actual lessons.
That being said, it's certainly possible to add a callout in that episode noting that the ``` syntax is available (though the release of The Carpentries Workbench in May will render this guide obsolete.
This maybe more of a question/discussion instead of an issue.
Should we also include the usage of fenced code blocks (i.e. triple backticks ```) in the formatting chapter ?
Also I don't understand what would the
method have over the ``` method?
Is there some additional functionality that it brings ?
The text was updated successfully, but these errors were encountered: