Add markdown feature parser - #353
Merged
Merged
Conversation
Parse specifications written as GitHub-flavoured markdown so they render nicely on GitHub. Headings carry the keywords, steps are list items, doc-strings are fenced code blocks, tables are markdown tables, and comments use `>` blockquotes (visible) or `<!-- -->` (hidden). MarkdownFeatureParser emits the same events as FeatureParser into the shared state machine, so a markdown feature and its .feature equivalent parse to identical output. Common logic is extracted into BaseFeatureParser and BaseFileParser. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
MarkdownFeatureParserandMarkdownFeatureFileParserfor parsing specifications written as GitHub-flavoured markdown, so they render nicely on GitHub.# Feature:,## Scenario:), steps are list items, doc-strings are fenced code blocks, and data/example tables are markdown tables. Comments use>blockquotes (visible callouts) or<!-- -->(hidden).FeatureParserinto the shared state machine, so a markdown feature and its.featureequivalent parse to identical output. Common logic extracted intoBaseFeatureParserandBaseFileParser.<etc.) are decoded in prose but left verbatim inside doc-strings; inline code spans are not yet exempt from decoding.examples/markdown/package and unit tests covering every construct plus the markdown/.featureequivalence guarantee.