Repository navigation
Conversation
lightdash-bot
added
the
cloudy-needs-review
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Documentation validation✅ All blocking checks passed. Component system0 finding(s) across the corpus. Findings on lines this pull request touched are annotated inline in Files changed. |
jpetey75
deleted the
cloudy/docs-explain-what-auto-y-axis-range-actually-does-in-ch-097fee9e
branch
October 23, 2026 16:10
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The Axes section of the chart configuration docs said you could "keep the default auto y-axis range" but never explained what that auto range actually does, so readers assumed turning it on would always zoom the axis in on their data.
Adds a short "Auto y-axis range" subsection explaining the real rule: auto range only drops 0 as the axis minimum when the lowest value is more than 3 times the spread between the lowest and highest values. Data sitting closer to 0 relative to its spread keeps 0 as the minimum even with auto on — for example, percentages ranging roughly between 30% and 80% still start at 0. The same rule applies to the maximum for entirely negative data. The new text also notes this only applies to line, area, and scatter axes (bar axes always start at 0), and points readers to the manual Min/Max fields as the way to force a narrower range.
A teammate answered a support question that the docs should have covered. Written by Cloudy's docs writer; a teammate reviews it before merge, and edits are welcome.