-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Gauge] Vis Type #126048
[Gauge] Vis Type #126048
Conversation
@elasticmachine merge upstream |
…ibana into gauge-transparent-background
@elasticmachine merge upstream |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanx Yaroslav for working on it! Some comments from my side:
- In vislib the users can ovewrite the gauge colors from the legend. These colors are saved with the SO (uiState). Although we dont support the legend yet, I think that we should respect the overwritten colors. So for example this is a gauge with overwritten color (orange) but when I open it on the new implementation, the color is not respected
- When I have a saved gauge with small multiples, and then render it with the new implementation, the user sees only one chart (makes sense as we dont support it). Can we add a warning in that case? We are doing the same for heatmap so it will be easy to integrate it.
- The percentage mode returns different results for the new implementation.
'visTypeGauge.controls.gaugeOptions.showOutlineNotAvailable', | ||
{ | ||
defaultMessage: | ||
'The outile is not supported with the new charts library. Please, enable the gauge legacy charts library advanced setting.', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The outline (fix typo)
title: 'Heatmap', | ||
description: 'Creates a heatmap viz', | ||
icon: 'visHeatmap', | ||
name: 'gauge', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This mock is for heatmap, why have we altered this?
We've discussed with @stratoula in the private chat, that I'm going to implement Percentage mode is going to be ready very soon: #126318. |
@Kunzetsov the plan is to create additional PRs for the colouring and percentage mode and merge them to this PR or are we going to merge this PR in main and then the additional PRs? |
@stratoula, To the main one by one. |
@Kunzetsov I see that you have hidden the Add bucket btn This is correct of course as we don't support it but I am not very fond of the fact that we have a buckets title without any action. I can think 3 things to improve it:
It might not be so important as the new implementation won't be the default one but I would like yours and Joe's thoughts on that cc @flash1293 . |
@stratoula, totally makes sense. I'll implement it right now. I didn't know, that we have heatmap when I was implementing this approach ) |
Like that approach @stratoula |
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Module Count
Public APIs missing comments
Async chunks
Public APIs missing exports
Page load bundle
Unknown metric groupsAPI count
async chunk count
ESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: cc @Kunzetsov |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I approve it as it does what it says. The percentage mode and the uiState doesn't work but we have follow up PRs for them. With that being said, I am approving it (not a fan of merging PRs with bugs though :D )
Summary
Completes part of the issue
Disabled options for elastic charts
elastic-charts.options.mov
Goal
Gauge
Split chart warnings