## Context
Follow-up to #21293 (merged). That PR added a bespoke
`relationTableFilter` to keep a relation field rendered as a
record-table widget scoped to the host record. It turns out to be
redundant.
## Why it's redundant
The relation table widget's view already carries an
`isCurrentRecordSelected` relation filter on the inverse field — it's
baked in by `useAddDraftViewForFieldRelationTableWidget` when the widget
is configured. That filter is resolved through the `currentRecordId`
that `FieldWidgetRelationTable` provides via
`RecordFilterValueDependenciesContext`, and
`turnRecordFilterIntoGqlOperationFilter` turns it into exactly `{
`${inverseField}Id`: { in: [recordId] } }`.
So the hand-built `relationTableFilter` duplicated a filter the existing
mechanism already produces from `currentRecordId`.
## Changes
- Remove `relationTableFilter` from
`RecordFilterValueDependenciesContext`
- Stop reading/applying it in `useFindManyRecordIndexTableParams` and
`useAggregateRecordsForRecordTableColumnFooter`
- Delete the `getRelationTableFilter` util and its test
- `FieldWidgetRelationTable` provides `currentRecordId` only
Net −263 lines; relies on the existing `isCurrentRecordSelected` +
`currentRecordId` scoping path.
<!-- This is an auto-generated description by cubic. -->
<a
href="https://cubic.dev/pr/twentyhq/twenty/pull/21965?utm_source=github"
target="_blank" rel="noopener noreferrer"
data-no-image-dialog="true"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source
media="(prefers-color-scheme: light)"
srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img
alt="Review in cubic"
src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a>
<!-- End of auto-generated description by cubic. -->
Charles Bochet
b1ada79d72
