-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Code blocks in requirements break parsing #280
Comments
I think I can solve this by adding a new state in the markdown parser that ignores literal sections (starting and ending with tripple-backticks). |
Similar behavior when requirement ids are in the blocks Example ...
```markdown
### Chatting with AI
`req~ai.chat.new-message-based-on-previous~1`
```
Then, at the implementation, a comment is added this implementation is covered:
```java
} else if (keyEvent.getCode() == KeyCode.UP) {
// [impl->req~ai.chat.new-message-based-on-previous~1]
``` |
I checked the GMF spec from which the fenced code blocks come. That spec allows quite a range of variants to start a code block. I tried to capture the reasonable part in the parser in #433 without making it a lot more complex. |
* #280: Inside Markdown code blocks requirements are now ignored (see https://github.github.com/gfm/#fenced-code-blocks for specification).
Adding a code block like:
... to the requirements file breaks the parsing. OFT seems to detect it as a new requirement.
Expected Behaviour:
The text was updated successfully, but these errors were encountered: