You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
When extending the width of the browser in which DBT Docs is served over a specific threshold the scrollbar for the details section of a source / model disappears and an ugly set is overleft that extents over the borders of the screen.
Expected Behavior
I would expect to have the details not in a horizontally scrollable HTML element, but rather as tiles without the need to scroll horizontally. Having long links or descriptions in it makes it cumbersome to scroll to the information that you need.
Steps To Reproduce
Include several different information to the meta section in a source's / model's yaml file
Serve dbt docs
go to a model / source in the UI
Extend the width of the browser if not already in fullsize view
SeppBerkner
changed the title
[Bug] Meta data in DBT Docs extents outside screen with no scrollbar
[Bug] Meta data in DBT Docs extends outside screen with no scrollbar
Sep 17, 2024
Is this a new bug in dbt-core?
Current Behavior
When extending the width of the browser in which DBT Docs is served over a specific threshold the scrollbar for the details section of a source / model disappears and an ugly set is overleft that extents over the borders of the screen.
Expected Behavior
I would expect to have the details not in a horizontally scrollable HTML element, but rather as tiles without the need to scroll horizontally. Having long links or descriptions in it makes it cumbersome to scroll to the information that you need.
Steps To Reproduce
meta
section in a source's / model's yaml fileRelevant log output
No response
Environment
Which database adapter are you using with dbt?
postgres
Additional Context
No response
The text was updated successfully, but these errors were encountered: