Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(swagger-ui-web-component): ensure there are 4 grid columns for each operation #1422

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Mierenga
Copy link
Contributor

@Mierenga Mierenga commented May 23, 2024

Summary

Currently there is some CSS that has 3 columns, but a recently upgraded version of Swagger UI regrouped the elements so that it is now necessary to have 4 columns to prevent the open/collapse toggle button from flowing into the next row.

The current CSS rule that is offending is:

.swagger-ui .opblock .opblock-summary {
  grid-template-columns: 80px auto 30px;
}

before:
Screenshot 2024-05-23 at 3 27 45 PM

after:
Screenshot 2024-05-23 at 3 28 02 PM

Resources

@Mierenga
Copy link
Contributor Author

Need to verify this has the expected result, but wanted to throw up this PR since I noticed the issue

…ch operation

Currently there is some CSS that has 3 columns, but a recently upgraded version of Swagger UI regrouped the elements so that it is now necessary to have 4 columns to prevent the open/collapse toggle button from flowing into the next row.

The current CSS rule that is offending is:
```css
.swagger-ui .opblock .opblock-summary {
  grid-template-columns: 80px auto 30px;
}
@kongponents-bot
Copy link
Collaborator

Preview components from this PR in consuming application

In consuming application project install preview versions of shared packages generated by this PR:

@kong-ui-public/swagger-ui-web-component@pr-1422
@kong-ui-public/spec-renderer@pr-1422

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