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

fix: double icons in display name column on package systems table #1183

Merged
merged 2 commits into from
May 22, 2024

Conversation

mkholjuraev
Copy link
Collaborator

@mkholjuraev mkholjuraev commented May 10, 2024

Description

Associated Jira ticket: No ticket needed

A small fix for the double icons on the package systems page. As the page completely uses the inventory table and also there were extra column definition, double icons appeared. Removing the extra one fixes it.

I am not sure even if this icon should be displayed in package systems table. I will consult it with the ux.

How to test the PR

Please include steps to test your PR.

Before the change

After the change

Dependent work link

Checklist:

  • The commit message has the Jira ticket linked
  • PR has a short description
  • Screenshots before and after the change are added
  • Tests for the changes have been added
  • README.md is updated if necessary
  • Needs additional dependent work

@mkholjuraev mkholjuraev requested a review from a team as a code owner May 10, 2024 09:37
@mkholjuraev mkholjuraev marked this pull request as draft May 10, 2024 09:47
@mkholjuraev mkholjuraev marked this pull request as ready for review May 10, 2024 10:31
@@ -95,14 +95,6 @@ export const advisorySystemsColumns = () => [
];

export const packageSystemsColumns = [
{
key: 'display_name',
Copy link
Member

@bastilian bastilian May 10, 2024

Choose a reason for hiding this comment

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

I think we still have to have 'display_name' as a string in the columns definition. That way the Inventory knows where we want to show the display_name column, but we won't override the default column.

... I believe { key: 'display_name' } might work too.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I believe we are safe to remove this column definition. Because, the inventory module merges those columns by default to those patch related columns that we pass in.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I have removed tags column definition as well as it is also not necessary

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 63.83%. Comparing base (42e843c) to head (4ce945f).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1183      +/-   ##
==========================================
- Coverage   63.84%   63.83%   -0.02%     
==========================================
  Files         124      124              
  Lines        3225     3224       -1     
  Branches      826      826              
==========================================
- Hits         2059     2058       -1     
  Misses       1166     1166              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@mkholjuraev mkholjuraev requested review from bastilian and a team May 15, 2024 09:26
Copy link
Contributor

@gkarat gkarat left a comment

Choose a reason for hiding this comment

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

LGTM, thanks @mkholjuraev

@mkholjuraev mkholjuraev merged commit 7f7bc89 into RedHatInsights:master May 22, 2024
1 of 2 checks passed
@mkholjuraev
Copy link
Collaborator Author

🎉 This PR is included in version 1.67.6 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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.

None yet

4 participants