Upgrade echarts to 5.1.2 #1099
Merged
Upgrade echarts to 5.1.2 #1099
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
crnjan
force-pushed
the
feature/echarts_upgrade_to_5_1_1
branch
2 times, most recently
from
1ca194c to
a0b1e3d
Compare
Job #160: Bundle Size — 10.46MB (0%).
|
Signed-off-by: Boris Krivonog <[email protected]>
crnjan
force-pushed
the
feature/echarts_upgrade_to_5_1_1
branch
from
a0b1e3d to
5cd1044
Compare
|
Why not v5.1.2 with even more fixes? |
|
At the time I created my branch 5.1.2 did not yet exist :) Will update my PR ... |
Signed-off-by: Boris Krivonog <[email protected]>
ghys
approved these changes
Jun 10, 2021
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.
When displaying two values using a single gauge, on initial load gauge(s) are not rendered correctly, as per screen:
switching a tab or similar action fixes the problem
After upgrade to 5.1.1. this cannot be reproduced anymore - a similar discussion here.
Signed-off-by: Boris Krivonog [email protected]