Bug with about remark-usage

[wooorm]

You need to provide much more info. All tests are working as expected.

[niftylettuce]

See #8

[wooorm]

😨

Could you add a test case that used to fail, but now doesn't anymore, so we can prevent this in the future?

[niftylettuce]

@wooorm not sure what I did to cause it yet tbh 😆

[wooorm]

Seems to be based on the example you have it!

[niftylettuce]

@wooorm it was because of a missing closing HTML tag in my markdown - I'm not sure how to write a test case for this. e.g. // <sub>Some foo bar baz (note the missing </sub>)

[niftylettuce]

@wooorm can you figure out how to write a test for this? here was my example file (note the missing closing tag for </sub> at the very top

// <sub>This section is automatically rendered from [example.js](example.js).

// ### Install

// [npm][]:

console.log('sh', 'npm install -g sao');
console.log('sh', 'sao lass new-project');

// [yarn][]:

console.log('sh', 'yarn global add sao');
console.log('sh', 'sao lass new-project');

// ### Structure

console.log(
  'sh',
  require('child_process').execSync('tree new-project').toString()
);

[wooorm]

Take a look at the fixtures!

1. You don’t need to touch test/index.js, just create a new fixture directory with the correct files (look at ones already there).
2. I’d also suggest using a name like issue-7 and linking to this issue in readme.md!
3. Also try to use the shortest example.js possible: try to keep only the failing lines!

[wooorm]

Anyway, let’s talk over on GH-8 on how to implement the fix!