Skip to content

fix(style): reduce padding on inline code blocks in markdown (#7569)#10789

Open
adrianodpdiaz wants to merge 3 commits intoswagger-api:masterfrom
adrianodpdiaz:code_blocks_are_overlapping_due_to_high_padding
Open

fix(style): reduce padding on inline code blocks in markdown (#7569)#10789
adrianodpdiaz wants to merge 3 commits intoswagger-api:masterfrom
adrianodpdiaz:code_blocks_are_overlapping_due_to_high_padding

Conversation

@adrianodpdiaz
Copy link
Copy Markdown
Contributor

@adrianodpdiaz adrianodpdiaz commented Apr 1, 2026

Description

This PR reduces the vertical padding on inline code blocks in markdown to prevent them from overlapping adjacent elements in API descriptions.

The issue is more visible in dark mode, but also happens in light mode, for all HTTP method types.

Motivation and Context

#7569

Screenshots:

Example of style before (DELETE method):
before_dark
before_light

Example of style after (DELETE method):
after_dark
after_light

Checklist

My PR contains...

  • No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
  • Dependency changes (any modification to dependencies in package.json)
  • Bug fixes (non-breaking change which fixes an issue)
  • Improvements (misc. changes to existing features)
  • Features (non-breaking change which adds functionality)

My changes...

  • are breaking changes to a public API (config options, System API, major UI change, etc).
  • are breaking changes to a private API (Redux, component props, utility functions, etc.).
  • are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
  • are not breaking changes.

Documentation

  • My changes do not require a change to the project documentation.
  • My changes require a change to the project documentation.
  • If yes to above: I have updated the documentation accordingly.

Automated tests

  • My changes can not or do not need to be tested.
  • My changes can and should be tested by unit and/or integration tests.
  • If yes to above: I have added tests to cover my changes.
  • If yes to above: I have taken care to cover edge cases in my tests.
  • All new and existing tests passed.

@adrianodpdiaz
Copy link
Copy Markdown
Contributor Author

Hi @char0n @glowcloud — another small style fix. I appreciate if you have a chance to review!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants