Why doesn’t this code:
var www_server = Sealious.ChipManager.get_chip("channel", "www_server");
www_server.route({
method: "GET",
path: "/users.csv",
handler: function(context, request){
// .. logic goes here
preserve newlines? Did the syntax change or is there something I am missing?
「いいね!」 1
gkln
2016 年 8 月 10 日午前 10:58
2
You should encapsulate the code block with ``` instead of `.
var www_server = Sealious.ChipManager.get_chip("channel", "www_server");
www_server.route({
method: "GET",
path: "/users.csv",
handler: function(context, request){
// .. logic goes here
「いいね!」 2
Please take a look at the source of my message: I am using ```…
cpradio
(cpradio)
2016 年 8 月 10 日午前 11:35
4
It seems to be the extra space after the closing ```
「いいね!」 3
I see, removing the redundant space does fix the issue.
But It’s not CommonMark compliant, right? When I pasted the code [here] it behaved as it should.
「いいね!」 1
cpradio
(cpradio)
2016 年 8 月 10 日午後 1:12
6
Discourse isn’t using CommonMark yet (to my knowledge) so if it works at http://spec.commonmark.org/dingus/ , when Discourse switches to CommonMark, it should resolve itself.
「いいね!」 2
eviltrout
(Robin Ward)
2016 年 8 月 10 日午後 2:45
7
Yes I can confirm we’re note on CommonMark yet. In 1.6 I did a lot of work to convert our existing markdown to ES6 so that we could try plugging in a different engine and see how well it works.
「いいね!」 5
sam
(Sam Saffron)
2017 年 6 月 26 日午後 2:04
8
Rebaked OP and all seems fine
trailing spaces
no
longer
break this
Per our migration plans , I just enabled markdown.it at Meta.
It is an excellent CommonMark compliant engine. I expect quite a few edges to be found during this period of testing.
Do not open bugs about the new Engine, just reply here.
I/we will be updating the top post here with the list of issues and striking out stuff as it is fixed.
Current known issues (to be fixed)
Onebox vanishes after you start typing and works not-super consistently
pendin…
「いいね!」 3