Snippits containing self-closing angle bracket components break markdown parsing

[jrowlingson]

No description provided.

[kpatelsecondst]

Does this workaround render self-closing brackets too?

[crixx]

Any news on this or other ideas apart from using hbs?

Actually the rendering is only broken if the "custom tag" is NOT in lowercase. As soon as the tag is in lowercase, it works. Ember templates with angle-brackets ar per default camel-case, this seems to be a quite reasonable scenario 😬

@kpatelsecondst : Nope, the work around doesn't fix this.
The problem is, that after the code-block, markdown doesn't get rendered anymore - it's rendered inside the code block.

Here some examples that break the markdown parsing.

<X />

## Header
--
<X class="foo" />

## Header
--
<X class="foo" 
/>

## Header
-- 
<X
@something="something"
/>

## Header

[kpatelsecondst]

@crixx : My mistake, markdown does indeed break. The only temporary workaround would probably be to use html header tags until markdown parsing is fixed.

[barryofguilder]

I think this might still be an issue. We are still seeing this for our self closing components in the demo.example component.

{{#docs-demo as |demo|}}
  {{#demo.example name="docs-icon-basic.hbs"}}
    <UiIcon @icon="rocket" />
  {{/demo.example}}

  {{demo.snippet "docs-icon-basic.hbs"}}
{{/docs-demo}}

The above code will cause any markdown headers below it to not work.

[samselikoff]

@barryofguilder I haven't been working on this lately but best bet is probably to open a new issue.

If someone wants to help this project the most important thing is probably to triage/prioritize issues. We should prioritize bug fixes first. Octane stability I would deprioritize until it's stable.