Update markdown parser config to fix issue with broken line breaks handling in resource descriptions #7613
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
Although we have a markdown parser rendering descriptions, it turns out when we use the 'zero' parser it disables the break handling we are using it for resulting in descriptions not being able to be multi-line.
This PR fixes that by using the default markdown parser. This does have the side-effect of rendering more markdown syntax. I think this is okay if we treat it as an undocumented feature, and use it sparingly until we have some strong evidence that a majority of users are on 0.15 or above.
Reviewer guidance
Ping me if you want a channel to test this with, basically testing with any description containing line breaks will show the issue.
References
…
Contributor Checklist
PR process:
Testing:
Reviewer Checklist
yarn
andpip
)