fix: Padding improvement when no axes are shown #774
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
christopherkindl
approved these changes
Oct 24, 2023
|
🎉 This PR is included in version 3.11.0-beta.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
severinlandolt
added a commit
that referenced
this pull request
Nov 6, 2023
* fix: tab colors (#768) * feat: Legend scroll (#716) * Add label rotation * fix: Padding improvement when no axes are shown (#774) * fix: value test circle * fix: Transitions Input elements (#776) * feat: Textarea (#778) * feat: add spark charts (bar, line, area) (#759) --------- Co-authored-by: mbauchet <maximebauchet26@gmail.com> Co-authored-by: Severin Landolt <sev.landolt@gmail.com>
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.
Description
Closes #773
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
How has this been tested?
Screenshots (if appropriate):
The PR fulfills these requirements:
mainbranch