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

[NIFI-12537] Open cluster/node dialog from Summary screen. #8454

Merged
merged 6 commits into from
Feb 29, 2024

Conversation

rfellows
Copy link
Contributor

NIFI-12537

  • Refactored the Summary Listing tables to all extend an abstract base class to reduce code duplication
  • Created an abstract base class for the cluster dialog tables
  • Added cluster node filtering dropdown when in clustered mode on the summary screen

@rfellows rfellows added the new ui Pull requests for work relating to the new user interface being developed. label Feb 27, 2024
@mcgilman
Copy link
Contributor

Will review...

Copy link
Contributor

@mcgilman mcgilman left a comment

Choose a reason for hiding this comment

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

Nice work @rfellows! The shared filter component and base class for the cluster status table nicely avoid repeated boilerplate as much as possible. I did notice a couple of things detailed below and a separate observation that affects all tables. As I was verifying the sort (and multi-sort) capabilities and clicking on the headers the text kept selecting. I'd be interested to get your thoughts on possibly disabling that by setting user-select: none for all mat-sort-header-content in the base styles.scss.

}
});
}),
catchError((error) => of(this.errorHelper.handleLoadingError(error.error, error)))
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think we want to be using handleLoadingError here. I think we probably want to check the error and see if it should be shown in context and then either use a snackbar or full screen. handlingLoadingError accepts an argument that is the current store status and uses that as part of the logic to determine how to sure the error message.

}
});
}),
catchError((error) => of(this.errorHelper.handleLoadingError(error.error, error)))
Copy link
Contributor

Choose a reason for hiding this comment

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

Same as above.

private _clusterNodes: NodeSearchResult[] | null = null;
private _selectedClusterNode: NodeSearchResult | null = null;
private _selectedId: string | null = null;
private currentFilter: SummaryTableFilterContext | null = null;
Copy link
Contributor

Choose a reason for hiding this comment

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

This doesn't appear to be used (though maybe I missed it).

@rfellows
Copy link
Contributor Author

As I was verifying the sort (and multi-sort) capabilities and clicking on the headers the text kept selecting. I'd be interested to get your thoughts on possibly disabling that by setting user-select: none for all mat-sort-header-content in the base styles.scss.

I agree. We have many issues in the app allowing too much text selection. I can add this to the base listing table style since it happens so regularly when just clicking on the headers to sort them.

Copy link
Contributor

@mcgilman mcgilman left a comment

Choose a reason for hiding this comment

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

Thanks for the updates @rfellows! Will merge once CI completes.

@mcgilman mcgilman merged commit 455159f into apache:main Feb 29, 2024
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new ui Pull requests for work relating to the new user interface being developed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants