Skip to content

Fixed ACTOR advanced filter recent regressions #12813

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

Merged
merged 1 commit into from
Jun 24, 2025

Conversation

lucasbordeau
Copy link
Contributor

This PR fixes recent regressions on advanced filters for the ACTOR field type.

  • The new isFilterable props on SETTINGS_COMPOSITE_FIELD_TYPE_CONFIGS wasn't taken into account for sub field picker in advanced filter.
  • A wrong component instance id was passed to subFieldNameUsedInDropdownComponentState

@lucasbordeau lucasbordeau requested a review from bosiraphael June 24, 2025 10:20
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

Fixed advanced filter regressions in ACTOR field type handling, improving filtering functionality in two key areas:

  • Added proper filtering of subfield options in packages/twenty-front/src/modules/object-record/advanced-filter/components/AdvancedFilterSubFieldSelectMenu.tsx to respect the isFilterable property from composite field configs
  • Fixed incorrect component instance ID handling in packages/twenty-front/src/modules/object-record/advanced-filter/components/AdvancedFilterDropdownFilterInput.tsx for subFieldNameUsedInDropdownComponentState

2 files reviewed, no comments
Edit PR Review Bot Settings | Greptile

Copy link
Contributor

🚀 Preview Environment Ready!

Your preview environment is available at: http://bore.pub:18831

This environment will automatically shut down when the PR is closed or after 5 hours.

@@ -32,7 +32,6 @@ export const AdvancedFilterDropdownFilterInput = ({
}: AdvancedFilterDropdownFilterInputProps) => {
const subFieldNameUsedInDropdown = useRecoilComponentValueV2(
subFieldNameUsedInDropdownComponentState,
filterDropdownId,
Copy link
Member

Choose a reason for hiding this comment

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

why this change? :)

Copy link
Member

@charlesBochet charlesBochet left a comment

Choose a reason for hiding this comment

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

Not sure about one change, I don't get it!

@charlesBochet charlesBochet merged commit 4834709 into main Jun 24, 2025
54 checks passed
@charlesBochet charlesBochet deleted the fix/actor-advanced-filter branch June 24, 2025 11:57
abdulrahmancodes pushed a commit to abdulrahmancodes/twenty that referenced this pull request Jun 26, 2025
This PR fixes recent regressions on advanced filters for the ACTOR field
type.

- The new `isFilterable` props on
`SETTINGS_COMPOSITE_FIELD_TYPE_CONFIGS` wasn't taken into account for
sub field picker in advanced filter.
- A wrong component instance id was passed to
`subFieldNameUsedInDropdownComponentState`
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