Hyperlink markdown doesn't work in Feature: section

[SubjectiveReality]

Hi- I'm trying to introduce SpecFlow and Pickles to my team, and one piece of feedback that came in was links to relevant Jira issues (or whatever) in places they may be needed in the feature files. I have tried the markdown after both Feature: and Scenario: keywords, and it works great after the latter but not after the former. Is this intentional for some reason? Seems like having the option to link from the Feature: area would be nice as well as the Scenario: area.

Btw, I'm generating via command line with the following: -trfmt=specrun -df=dhtml

Works (creates link in dhtml output):

Scenario: blah blah
[my link](https://my.link.com/blah)

Doesn't work (outputs unmodified text):

Feature: blah blah
[my link](https://my.link.com/blah)

[dirkrombauts]

Thanks for taking the time to report this. This behaviour is certainly not intentional. I will do my best to investigate it this week, but it might take me until next week - my real life schedule is quite full at the moment.

[SubjectiveReality]

No worries- it's a fantastic tool and your time and effort is much appreciated! I understand the busy schedule and am not worried about turn around time or anything like that. Glad the feedback was helpful and might try to track it down myself, schedule permitting.

Cheers

[dirkrombauts]

Thank you for your kind words.

[dirkrombauts]

I had a look at this ... the feature seems to work as expected, but could you please verify the following: Does the description part (that contains the link) start right next to the left margin?

I.e.

Scenario: blah blah
[my link](https://my.link.com/blah)

instead of

Scenario: blah blah
 [my link](https://my.link.com/blah)

The second version will cause Pickles to interpret the description as code instead of normal text.

[SubjectiveReality]

Wow, that was it, works fine without any indentation. Sorry about that, I completely missed the difference in how I had it in my working case and non-working case.

[dirkrombauts]

No problem ... it's a known issue, and shouldn't be too difficult to fix if you feel up to it: #302

[dirkrombauts]

Can this issue be closed?

[SubjectiveReality]

Yes, I think so. I'll take a look at that issue and see if I can help.

On Mon, Sep 12, 2016 at 11:17 AM, Dirk Rombauts notifications@github.com
wrote:

Can this issue be closed?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#367 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ3Z7YS_YmV3CCSuUBqcBO_adgy7XtjTks5qpYkTgaJpZM4J2McU
.