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

Present field selection table mass actions in a menu #1513

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

kiahna-tucker
Copy link
Member

@kiahna-tucker kiahna-tucker commented Mar 14, 2025

Issues

The issues directly below are completely resolved by this PR:
#1505

Changes

1505

The following features are included in this PR:

  • Replace the existing button group that surfaces field selection mass actions with a single button which will open a menu of field selection mass actions.

    • The button label for this CTA should be Mode.

    • Menu item content will consist of a header identifying a mass action and a (short) description of the action.

    • A radio button should be used to select a menu item.

    • The menu will consist of two actions located in the bottom, right corner: Cancel and Apply.

Tests

Manually tested

Approaches to testing are as follows:

  • scenarios you manually tested

Automated tests

N/A

Playwright tests ran locally

  • Admin
  • Captures
  • Collections
  • HomePage
  • Login
  • Materialization

Screenshots

Mode CTA disabled | Field selection view loading

pr_screenshot-1513-mass_action_menu-view_loading

Mode CTA enabled | Menu closed

pr_screenshot-1513-mass_action_menu-menu_closed

Mode CTA enabled | Menu open

pr_screenshot-1513-mass_action_menu-menu_open

@kiahna-tucker kiahna-tucker added the change:planned This is a planned change label Mar 14, 2025
@kiahna-tucker kiahna-tucker marked this pull request as ready for review March 14, 2025 18:02
@kiahna-tucker kiahna-tucker requested a review from a team as a code owner March 14, 2025 18:02
Comment on lines 248 to 251
'fieldSelection.massActionMenu.recommended.label': `Default`,
'fieldSelection.massActionMenu.recommended.description': `Allow the connector to dynamically select fields`,
'fieldSelection.massActionMenu.excludeAll.label': `Exclude All`,
'fieldSelection.massActionMenu.excludeAll.description': `Exclude non-essential fields`,
Copy link
Member

Choose a reason for hiding this comment

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

I could go either way - but it does seem a bit weird for one option to have All in the label and the other does not. But something like Default All is kinda odd.

loading={loading}
projections={projections}
selectedValue={
selectionAlgorithm === 'excludeAll' ? 'exclude' : 'default'
Copy link
Member

Choose a reason for hiding this comment

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

Why are we storing the algorithm so we have to use a ternary op?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
change:planned This is a planned change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants