fix: alignment of response description column in doc ui #8963
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.
Fix references to
.markdown
, since the class name is different when rendering in the OAS3 UI.Description
I added a comma-separated reference to
.renderedMarkdown
in the couple of places where.markdown
was used in the.scss
files, so that either class is treated equally. This was already done in several files, but one file was missed.Files that already handled either classname:
swagger-ui/src/style/_markdown.scss
swagger-ui/src/style/_models.scss
File that was missing it:
swagger-ui/src/style/_table.scss
Motivation and Context
Fixes #7850
The alignments are broken in the OAS3 UI for Response Model field descriptions.
How Has This Been Tested?
See screenshots below.
I also ran
npm run test
, and every test passed both when I was onmaster
and when I was on my branch.Screenshots (if appropriate):
Before:

After:

Checklist
My PR contains...
src/
is unmodified: changes to documentation, CI, metadata, etc.)package.json
)My changes...
Documentation
Automated tests