Skip to content

Conversation

@gpaoloni
Copy link
Collaborator

@gpaoloni gpaoloni commented Dec 4, 2025

Description

This PR addresses several UI fixes/polish described in the below linked ticket.

  • Replace strings for keyed translations.
  • Teams View “Actions” button converted to a primary button.
  • Updated the dropdown menu items text.
  • Updated the modal styling, replacing “return to…” icon and text in modal with history, for the back icon that we use in the Search results modal.
  • Moved the sorting arrows icon for sortable columns to align to the far right of each respective column.
  • Fixed UI weirdness: when the feature flag is turned off, the Skills column header has an awkward space between the title & the arrows.

Checklist

Verification steps

AFTER YOU MERGE

  1. Cut a release tag using the Github workflow. Wait for it to complete and notify in the #aselo-deploys Slack channel.
  2. Comment on the ticket with the release tag version AND any additional instructions required to configure an environment to test the changes.
  3. Only then move the ticket into the QA column in JIRA

You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P

@gpaoloni gpaoloni requested a review from stephenhand December 4, 2025 22:50
Copy link
Collaborator

@stephenhand stephenhand left a comment

Choose a reason for hiding this comment

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

Nothing blocking, just expressing a preference with the dialog props but you can leave as is if you feel strongly this approach is better

openDialog: boolean;
closeDialogHeader: string;
closeDialogContent: string;
closeDialogHeader: string | React.ReactElement;
Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm not such a fan of the string | ReactElement property pattern, I've worked with it before and find it a bit confusing to follow the component chain. If we need to stuff arbitrary elements in this section in some cases I'd rather just always pass an element, even if it is just a template tag, just to make modal configurations more consistent

closeDialogHeader: string;
closeDialogContent: string;
closeDialogHeader: string | React.ReactElement;
closeDialogContent: string | React.ReactElement;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Perhaps we could make this the children property to keep it consistent with the other modal

@gpaoloni gpaoloni merged commit 351163a into master Dec 8, 2025
23 checks passed
@gpaoloni gpaoloni deleted the gian_CHI-3547 branch December 8, 2025 23:06
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