Add ability to define requirements in Markdown files#66
Merged
Conversation
Settings from bullet lists are not yet extracted
"try_begin()" may fail to start a transaction if more than one product is collected in one "mantra collect" call. Switched to "begin()". Likely due to the prev. connection not being fully released when trying to aquire connection for the next product.
Tests explicit product-id filtering in frontmatter
Test content added to show how origin is displayed for reqs from Markdown files
This fits with GitHub's URL for files of any branch.
Explicitly stating product id makes switching between branches as base easier.
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.
Requirements may now be defined in Markdown files.
Mantra will search for Markdown files if
sourceis set toMarkup.The expected format follows: