fix(ui): isolate join table column preferences from list view#15846
Merged
GermanJablo merged 2 commits intoMar 4, 2026
Merged
Conversation
Add an e2e test that proves opening a join relationship table with admin default columns does not overwrite the related collection's main list column preferences.
Prevent join relationship tables from writing to collection-level list preference keys by always supplying parent metadata and persisting table preferences under the parent join path.
paulpopus
approved these changes
Mar 4, 2026
Contributor
|
🚀 This is included in version v3.79.1 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
admin.defaultColumnsdoes not overwrite the related collection list columns.Changes
Join relationship tables were persisting column preferences under the related collection key (for example,
collection-posts), which is also used by the main collection list view. This caused join table defaults to overwrite list view columns. The fix scopes join table preferences to the parent join path and provides parent metadata for all join fields so monomorphic joins are isolated as well.Testing
pnpm test:e2e joins --grep "should not overwrite list view columns when rendering relationship table with default columns"expect(locator('#heading-id')).toBeHidden() failed(ID column became visible after visiting the join field table)pnpm test:e2e joins --grep "should not overwrite list view columns when rendering relationship table with default columns"