[jira] Convert description to markdown #415
Merged
Conversation
This file contains 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
The description of an issue is now converted to markdown before we render the description. This is necessary because Jira returns the description in a wiki markup format, which doesn't look good when it is directly passed to the ReactMarkdown component for rendering. We also changed the logic to display the details of an issue, so that only the fields which are relly available are displayed in the details. This means if for example an issue doesn't have subtasks we do not display the subtasks section anymore. We also changed the color of the status label, so that the label matches the color in Jira. The previously used color field seems to be deprecated and Jira only allows 3 status categories. For these categories we set the color: "Done" -> "green", "In Progress" -> "blue" and "Open" -> "grey".
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| .replace(/~([^~]*)~/g, '<sub>$1</sub>') | ||
| .replace(/(\s+)-(\S+.*?\S)-(\s+)/g, '$1~~$2~~$3') | ||
| .replace( | ||
| /\{code(:([a-z]+))?([:|]?(title|borderStyle|borderColor|borderWidth|bgColor|titleBGColor)=.+?)*\}([^]*?)\n?\{code\}/gm, |
Check failure
Code scanning / CodeQL
Inefficient regular expression
| .replace(/^bq\.\s+/gm, '> ') | ||
| .replace(/\{color:[^}]+\}([^]*)\{color\}/gm, '$1') | ||
| .replace(/\{panel:title=([^}]*)\}\n?([^]*?)\n?\{panel\}/gm, '\n| $1 |\n| --- |\n| $2 |') | ||
| .replace(/^[ \t]*((?:\|\|.*?)+\|\|)[ \t]*$/gm, (match, headers) => { |
Check failure
Code scanning / CodeQL
Inefficient regular expression
|
|
||
| return str | ||
| .replace( | ||
| /^\n((?:\|.*?)+\|)[ \t]*\n((?:\|\s*?-{3,}\s*?)+\|)[ \t]*\n((?:(?:\|.*?)+\|[ \t]*\n)*)$/gm, |
Check failure
Code scanning / CodeQL
Inefficient regular expression
|
|
||
| return str | ||
| .replace( | ||
| /^\n((?:\|.*?)+\|)[ \t]*\n((?:\|\s*?-{3,}\s*?)+\|)[ \t]*\n((?:(?:\|.*?)+\|[ \t]*\n)*)$/gm, |
Check failure
Code scanning / CodeQL
Inefficient regular expression
Codecov Report
@@ Coverage Diff @@
## main #415 +/- ##
=======================================
Coverage 46.35% 46.35%
=======================================
Files 139 139
Lines 11776 11776
=======================================
Hits 5459 5459
Misses 6176 6176
Partials 141 141 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The description of an issue is now converted to markdown before we
render the description. This is necessary because Jira returns the
description in a wiki markup format, which doesn't look good when it is
directly passed to the ReactMarkdown component for rendering.
We also changed the logic to display the details of an issue, so that
only the fields which are relly available are displayed in the details.
This means if for example an issue doesn't have subtasks we do not
display the subtasks section anymore.
We also changed the color of the status label, so that the label matches
the color in Jira. The previously used color field seems to be
deprecated and Jira only allows 3 status categories. For these
categories we set the color: "Done" -> "green", "In Progress" -> "blue"
and "Open" -> "grey".