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
we see this <a name="test.js" href="fixtures/test.js">test.js</a> instead of [test.js](fixtures/test.js).
It is expected behavitor.
At first, the motivation of <a name> is used for anker link.( <a href="#test.js">Anker Link</a>. Markdown have not the same feature of name)
If we introduced pluginsConfig like "embed-template", this issue and #7 will be resolved, I think.
make the title optional in the future.
-- #18 (comment)
title: command/attribute? is good idea.
What do you think ? (If you're ok, I open a specific issue)
@azu Ok. After a second check, it seems that the problem comes from the asciidoc format that does not display properly the html code. In markdown everything is ok.
Activity
gdolle commentedon May 4, 2016
I think that it might be a good idea to make the title optional in the future.
For example:
[import, title:example](path/to/file.js)results to[import, title](path/to/file.js)results toWhat do you think ? (If you're ok, I open a specific issue)
azu commentedon May 4, 2016
@gdolle
It is expected behavitor.
At first, the motivation of
<a name>is used for anker link.(<a href="#test.js">Anker Link</a>. Markdown have not the same feature ofname)If we introduced
pluginsConfiglike "embed-template", this issue and #7 will be resolved, I think.title:command/attribute? is good idea.Ok. It will be separated issue.
gdolle commentedon May 4, 2016
@azu Ok. After a second check, it seems that the problem comes from the asciidoc format that does not display properly the html code. In markdown everything is ok.
Add title feature issue azu#19
Fix issue azu#18 and introduce code counter