warpfork / go-testmark Goto Github PK

https://spec.commonmark.org/0.30/#fenced-code-blocks

Worth clarifying that the testmark parser requires code fences to be three backticks or adding support for both valid forms of code fence. Let us not even talk about indented code blocks.

```
yer code
```

vs

~~~
yer code
~~~

I love testmark.

Apparently, the text after the characters indicating the start of a code block are called the "info string": https://spec.commonmark.org/0.30/#info-string

Currently the go-testmark code called it "BlockTag":

I like my name better, of course (I'm pretty sure someone would know what you mean faster when you say "the code block tag" than "the info string" until you bang them over the head with the spec link), but, ah well. It was a quick choice made without research.

Might as well follow the upstream lexicon as long as there is indeed a clear name specified for it.

After watching the GPN20 recording Testmark: a Markdown Convention for Test Fixtures and Data
I wanted to try out go-testmark.

After having a closer look, I realized that go-testmark is a golang library and not a "ready to run app". So I would need to write a tool myself to use it. Do you know if there is an app which uses this library?

Hi there. I was inspired by a talk in GPN so I took this as an exercise. I'm relatively new to (colaborative) software writing, so I didn't know how to do a pull request or how that works. Also there is two important things missing in python-testmark: some testing (ironically) and building it into a package. I will do this the next days (still learning) but for now I am happy to have you people have a quick look if I overlooked something. I'm somewhat baffled that this only took 40 lines of code.

Greetings
https://github.com/iameru/python-testmark