Fixed the Timeseries Chart/Interface Utilization Graph #275
Conversation
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
Collaborator
Author
|
@viniarck @rmotitsuki Just finished fixing the graphs. |
viniarck
approved these changes
Jul 21, 2025
Member
viniarck
left a comment
viniarck
left a comment
There was a problem hiding this comment.
It's great to have the new prop switch on k-interface component @HeriLFIU, it could've been derived but since it's already part of the API response too, it's great to have it as a prop too.
Leaving the PR pre-approved, it can land when the related PRs are approved and ready to land too. Also, Rogerio is on vacation this week.
HeriLFIU
force-pushed
the
UI/FixTimeseriesChart
branch
from
5f370d7 to
82e0582
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #274
Summary
The Interface Utilization Graph is fixed.
Local Tests
The Graphs displayed properly and no errors were thrown.
Related PRs
kytos-ng/ui#228
kytos-ng/kytos_stats#25