Skip to content
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

feat(Timeseries): Add total resource consumption in legend #108

Merged
merged 3 commits into from
Aug 2, 2024

Conversation

grafakus
Copy link
Contributor

@grafakus grafakus commented Aug 1, 2024

✨ Description

Related issue(s): -

Whenever the UI displays a single timeseries, the total resource consumption is displayed in the legend:
image

This PR also does some refactorings to prepare the integration of the Comparison view.

📖 Summary of the changes

See diff tab for specific comments

🧪 How to test?

-

Copy link
Contributor

github-actions bot commented Aug 1, 2024

Unit test coverage

Lines Statements Branches Functions
Coverage: 12%
12.62% (470/3724) 9.83% (138/1403) 9.49% (108/1137)

@simonswine
Copy link
Contributor

My only comment would be, I find the incosistency weird with the single value labels (again #95)

image

Copy link
Contributor

@simonswine simonswine left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@grafakus
Copy link
Contributor Author

grafakus commented Aug 2, 2024

My only comment would be, I find the incosistency weird with the single value labels (again #95)

I understand, it's a temporary state to provide a different view that I demoed to @bryanhuhta yesterday. Also, adding the total for each timeseries makes things unreadable in some cases:

image

@grafakus grafakus merged commit 1fbb2df into main Aug 2, 2024
5 of 6 checks passed
@grafakus grafakus deleted the feat/batch-of-improvements branch August 2, 2024 09:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants