Skip to content

AB#121666#2838

Open
AntoineRelief wants to merge 14 commits intonextfrom
AB#121666
Open

AB#121666#2838
AntoineRelief wants to merge 14 commits intonextfrom
AB#121666

Conversation

@AntoineRelief
Copy link
Copy Markdown
Collaborator

@AntoineRelief AntoineRelief commented Jan 6, 2026

Description

Implement per-row visibility for custom action buttons in grid widgets: each button now supports a filter that determines, on a record-by-record basis, whether the button is shown, and the action column width is computed from the number of buttons and label length instead of being hardcoded.

Type of change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)
  • Improvement (refactor or addition to existing functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

  • Open a grid widget settings and create 2+ custom row actions with the same columnLabel and different filters.
  • Verify that on each row, only the buttons whose filter matches are displayed.
  • Create buttons with different columnLabel values and verify one column per label is rendered.
  • Verify the column width adjusts to the number of buttons and label length.

Screenshots

image image

Checklist:

( * == Mandatory )

  • * I have set myself as assignee of the pull request
  • * My code follows the style guidelines of this project
  • * Linting does not generate new warnings
  • * I have performed a self-review of my own code
  • * I have put the ticket for review, adding the oort-backend team to the list of reviewers
  • * I have commented my code, particularly in hard-to-understand areas
  • * I have put JSDoc comment in all required places
  • * My changes generate no new warnings
  • * I have included screenshots describing my changes if relevant
  • * I have selected labels in the Pull Request, according to the changes with code brings
  • I have made corresponding changes to the documentation ( if required )
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

More explanation

https://www.loom.com/share/05a716d61b9744faaf51fb304c21d1e5?sid=f87cf896-582a-4f76-93ae-8ceed801b145

@GhaziAlibi GhaziAlibi requested a review from a team April 24, 2026 10:54
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.

2 participants