Feature/markdown output #557
Conversation
… inconclusive, test.
Static text placed in localization resource file for future translations. Some aspects still in builder for later refactoring when the path is clearer.
Included partial work on Generated Info feature.
Ready for refactoring.
parent class all return collections of lines.
Table formatting moved to own class TableBlock ScenarioOutline formatting added in class ScenarioOutlineBlock
Fixed bug #20 - Tags have double @ symbols
- In steps - In Tables
Stylist updated to process ScenarioHeading TestResult. Updated ScenarioBlock to process TestResult values. Acceptance tests updated to test Scenario Status
…o outline examples.
|
|
||
| internal virtual string AsFeatureHeading(string featureName) | ||
| { | ||
| var featureHeadingTemplate = "### {0}"; |
There was a problem hiding this comment.
I think it would be nice if it followed markdownlint rule MD001 heading-increment/header-increment - Heading levels should only increment by one level at a time.
|
It has been almost a year since this change was proposed, is this change going to be approved or declined? |
|
Hi @ColinM9991, Thank you for your interest in Pickles and this particular feature. I don't currently have time for Pickles - unfortunately. Real life is busy, and my professional focus has changed. So as things stand now, this change is not going to be approved in the forseeable future. If you want to take over management of Pickles, I will happily hand over everything to you and assist you in getting up and running. See #577 about that. |
|
Thanks for the update @dirkrombauts, unfortunately I'm in a similar situation and was curious as to whether this markdown feature had been considered as we're currently adopting Pickles in work for documentation purposes. |
|
What you could do is build pickles yourself from the VulcanAnalytics:feature/markdown_output branch. Then you would be one of the first people using the MarkDown format :-) |
|
Hi Colin, Dirk,
I too would have liked to be more involved with Pickles then I have of late.
I used the Markdown output feature with a client for several months the same way as Dirk suggested with a specifically compiled binary.
I may be able to help with a few bug fixes or a merge with the head branch to bing my branch up to date with the latest pickles release if you do go ahead with my branch/fork.
Darren Edward Comeau, MSc
Director / Consultant
E: Darren.comeau@vulcananalytics.co.uk
M: +44 (0)7403 419077
Vulcan Analytics Limited
Registered Company in England and Wales No. 08427757
…________________________________
From: Dirk Rombauts <notifications@github.com>
Sent: Wednesday, August 7, 2019 11:51:34 AM
To: picklesdoc/pickles <pickles@noreply.github.com>
Cc: Edward Comeau <edward.comeau@vulcananalytics.co.uk>; Author <author@noreply.github.com>
Subject: Re: [picklesdoc/pickles] Feature/markdown output (#557)
What you could do is build pickles yourself from the VulcanAnalytics:feature/markdown_output branch. Then you would be one of the first people using the MarkDown format :-)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#557?email_source=notifications&email_token=AG274QB75TGARVXXIQOW6GDQDKSLNA5CNFSM4F7LEQZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3YAFNY#issuecomment-519045815>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AG274QBZ7GKGN7GYLO7D7G3QDKSLNANCNFSM4F7LEQZA>.
|
|
It sounds like the best approach would be to form a group of individuals as owners to maintain the codebase. I'd be happy to progress with initial discussions, introductions etc if we have some volunteers. |
|
Thank you for you comments, folks. I will keep you in mind! |
|
@darrencomeau I know you've been waiting for a long time for this, thank you for your patience! |
|
Released in version v2.21.0. |
Work In Progress - #237