fix: Use preformatted text for purl and cpe when writing markdown - #15
Open
bol0gna wants to merge 1 commit into
Open
fix: Use preformatted text for purl and cpe when writing markdown#15bol0gna wants to merge 1 commit into
bol0gna wants to merge 1 commit into
Conversation
anthonyharrison
requested changes
Jun 25, 2026
anthonyharrison
left a comment
anthonyharrison
left a comment
Owner
There was a problem hiding this comment.
Not sure this is the correct approach. purl and cpe are already initialised to "" on line 125
If there is an issue with the processing of purls and cpes then the change needs to apply to all types of document not just Markdown.
Do you have a simple SBOM which demonstrates the issue?
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
2 participants
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.
I made a markdown doc and went to preview it, but the
cpefield includes asterisks and somepurls may have underscores. Since markdown uses these to italicize text, I figured we could instead wrap those columns' content in ``.Not sure if there's a better way to do this than
isinstanceso feel free to do it differently