Skip to content

Conversation

agrare
Copy link
Member

@agrare agrare commented Sep 26, 2025

This should really be a green check or a red X but I'm not sure how best to do that, @GilbertCherrie ? One of the col_formats maybe?

image

@agrare agrare requested a review from a team as a code owner September 26, 2025 18:27
@GilbertCherrie
Copy link
Member

@agrare I'm not sure what this pr is for, can you include screenshots of where in the UI you want these icons

@Fryguy
Copy link
Member

Fryguy commented Sep 26, 2025

@agrare I don't think we should show the error on the list view page - the valid/invalid is sufficient and they can click through for the error.

@GilbertCherrie The new Valid column. Ideally it show show a check or x like we do for compliant on vms.

- repository
- created_at
- updated_at
- payload_valid
Copy link
Member

Choose a reason for hiding this comment

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

Presentation wise I think put these before the dates.

@agrare
Copy link
Member Author

agrare commented Sep 26, 2025

I don't think we should show the error on the list view page

Yeah I was thinking we could do a tooltip over the invalid X if possible, if not I can drop it and just show on the details page

@agrare agrare force-pushed the add_payload_valid_payload_error_columns branch from 02f0b33 to a9c8ad5 Compare September 26, 2025 20:01
@GilbertCherrie
Copy link
Member

@agrare I updated this pr with the icons for the table
Screenshot 2025-09-29 at 3 55 44 PM

@agrare
Copy link
Member Author

agrare commented Oct 6, 2025

Awesome thanks @GilbertCherrie , do you know if there is a way to show just the icon and not True/False after it?

@GilbertCherrie
Copy link
Member

Awesome thanks @GilbertCherrie , do you know if there is a way to show just the icon and not True/False after it?

I'm not sure but I can check

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.

3 participants