Skip to content

feat: implement simple and narrow vertical progress bar #1560

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

Merged
merged 8 commits into from
Nov 2, 2024

Conversation

astandrik
Copy link
Collaborator

@astandrik astandrik commented Oct 30, 2024

Stand Stand

Closes #1190

CI Results

Test Status: βœ… PASSED

πŸ“Š Full Report

Total Passed Failed Flaky Skipped
134 134 0 0 0

Bundle Size: πŸ”Ί

Current: 79.20 MB | Main: 79.19 MB
Diff: +0.01 MB (0.01%)

⚠️ Bundle size increased. Please review.

ℹ️ CI Information
  • Test recordings for failed tests are available in the full report.
  • Bundle size is measured for the entire 'dist' directory.
  • πŸ“Š indicates links to detailed reports.
  • πŸ”Ί indicates increase, πŸ”½ decrease, and βœ… no change in bundle size.

},
align: DataTable.LEFT,
width: 85,
resizeMinWidth: 40,
Copy link
Contributor

Choose a reason for hiding this comment

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

It looks strange when resized. Let's do either with fixed bar width or non-resizable column.
Screenshot 2024-10-31 at 18 16 58

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

reworked

@@ -111,6 +118,57 @@ export function getMemoryColumn<
resizeMinWidth: 170,
};
}

export function getRAMColumn<T extends {MemoryUsed?: string; MemoryLimit?: string}>(): Column<T> {
Copy link
Member

Choose a reason for hiding this comment

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

There is no sorting for new columns if table is paginated.

Currently, for every column name is checked with isSortableNodesProperty, if name is in the list, the column is sortable and it's name is sent to backend as sort param.

I'm not sure what's to do in this case, since there are two columns with different ids, but they have the same sort fields (CPU and Memory).

Probably, you can use not column name, but add separate sortField property to every column object (in such case it's better to do it in a separate PR, since it's a lot of refactoring). Maybe there is a better and easier solution

Copy link
Collaborator Author

@astandrik astandrik Nov 1, 2024

Choose a reason for hiding this comment

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

created dictionary for sort values

not sure if it's the best solution in the world, but as far as we decided to rename CPU to Pools looks like there are not so many choices left...

@astandrik astandrik added this pull request to the merge queue Nov 2, 2024
Merged via the queue into main with commit e5d0823 Nov 2, 2024
6 checks passed
@astandrik astandrik deleted the astandrik.vertical-progress-bar-1190 branch November 2, 2024 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

implement simple and narrow vertical progress bar
3 participants