Save a view field and its scope view in one metadata migration
Server half of saving a column from the Edit column panel. Today the front saves a column and its scope as a chain of mutations (view field, scope view, filter groups, filters, sorts), each its own workspace migration: about 4.6 s of requests for a new scoped column. This PR adds one mutation that does it in a single migration (~0.4–0.5 s for the same payload, API only). The front switches to it in #30349.
Changes
upsertViewFieldWithScope(metadata schema,ViewFieldResolver): takes the view field (id,viewId,fieldMetadataId, optionalisVisible,isCanonical,size,position,aggregateOperation,settings) andscope: { viewFilters, viewFilterGroups, viewSorts } | null. Creates the view field if missing, otherwise updates only the sent properties. An omitted scope keeps the current one; a null or empty scope removes the scope view; otherwise the scope view is created asTABLE_WIDGETon the relation's target object, or kept and its children diffed by id (the client's ids are kept). Returns{ viewField, scopeView }.- One migration: every operation goes through a single
validateBuildAndRunWorkspaceMigration, so the scope validators from #30341 check the final state. - Shared diff: the filter / filter group / sort diff moves out of
ViewWidgetUpsertServiceintobuildViewFiltersAndSortsUpsertFlatOperations, used by both. On update, an omitted value keeps the stored one andnullclears it; a filter group is only rewritten when a value actually changes, and a filter keeps its group when an update omits it. A sort'ssubFieldNameis now accepted and kept. - Behaviour change on
upsertViewWidget: an explicitnullforparentViewFilterGroupId,positionInViewFilterGroup,viewFilterGroupIdorsubFieldNameused to keep the saved value and now clears it, and sorts now acceptsubFieldName. The in-repo front sendsundefinedfor unchanged values, so the app is unaffected; an API or SDK client that sentnullmeaning "unchanged" would now clear the value. This matches whatnullmeans everywhere else in the metadata API. - One visibility rule: a scope view inherits its owner column's view visibility and creator through
inheritScopeViewOwnerVisibility, used byViewService.createOneand the new mutation. - Permissions: the view field and view-child guards already used by the chain (same declaration as
updateViewFieldin the endpoint permission snapshot); a request whoseviewIddiffers from the existing view field's view is rejected. - Lookup columns: the input also takes
relationTargetFieldMetadataId(#30472), so the Edit column panel saves a lookup column with its scope in one request. - Client SDK and front metadata schema regenerated.
Stack
This PR targets felix/relaxed-einstein-vxil3q-base-scope-save, an integration branch merging #30339, #30341 and #30472, so the diff shows only this PR.
The work is split into short tracks that can be reviewed and merged in parallel. Each PR targets main or the one PR it builds on. Two PRs need several others; they target an integration branch (felix/relaxed-einstein-vxil3q-base-*, not a PR) that merges exactly their dependencies, so their diff shows only their own changes. A PR can merge once everything in its "Builds on" column is merged; retarget it to main at that point.
Size counts changed lines outside tests and generated files: S < 300, M 300–800, L > 800. Sizes are a snapshot and are not kept in sync with every push.
| Track | PR | What it does | Size | Code | Tests / generated | Builds on |
|---|---|---|---|---|---|---|
| Server: views | #30339 | Per-column settings on view fields (label, record limit) | S | +300 −2 | +703 −152 | main |
| Server: views | #30341 | A view can be owned by a one-to-many view field (scope view) | M | +584 −56 | +891 −4 | main |
| Server: views | #30472 | Lookup: a view field shows one field of its related record | M | +280 −38 | +428 −4 | #30339 |
| Server: views | #30466 👈 | upsertViewFieldWithScope: save a column with its settings, lookup and scope in one migration (~600 lines moved out of view-widget-upsert) | L | +1330 −567 | +1117 −256 | #30339, #30341, #30472 |
| Server: views | #30450 | Expose column scopes and lookups in the view AI tools | S | +31 | +222 | #30339, #30341, #30472 |
| Server: query engine | #30347 | Honor filter / orderBy / first on nested one-to-many relations | M | +462 −86 | +509 | main |
| Server: query engine | #30473 | One relation-selection tree through the common query layer (refactor, no behavior change) | L | +663 −685 | +277 −46 | #30347 |
| Server: query engine | #30465 | Each alias of a nested relation gets its own arguments and rows | L | +595 −237 | +727 −21 | #30473 |
| Front | #30468 | Query a relation under an alias with its own filter, sort and limit | S | +140 −19 | — | main |
| Front | #30469 | Don't recreate a saved sort that comes back under a new id | S | +21 −17 | +8 | main |
| Front | #30348 | Extra table columns and the Edit column panel, behind IS_COLUMN_SETTINGS_ENABLED | M | +718 −76 | +152 −30 | #30339 |
| Front | #30349 | Scope one-to-many columns from the Edit column panel | L | +1053 −92 | +316 −18 | #30348, #30466, #30468, #30469, #30465 |
| Front | #30439 | Lookup columns in the table, editable from their cells (absorbs #30440) | L | +805 −223 | +283 −30 | #30349 |
| Front | #30458 | Lookup and scoped columns on boards and calendars | M | +404 −284 | +140 −7 | #30439 |
The longest dependency chain is #30339 → #30348 → #30349 → #30439 → #30458; everything else is one or two levels deep. #30339, #30341 and #30472 each add a 2.59 instance command, so whichever merges after another may need a fresh timestamp.
Testing
- Integration
upsert-view-field-with-scope: create, replace and clear a scope; keep the scope when the input omits it; move a nested filter group to the root withnull; keep a filter in its group when an update omits it; clear a column's aggregate withnull; a new scope inherits an unlisted owner view's visibility and creator; a guest is denied, including through their own view. - Integration
upsert-view-widget,upsert-view-widget-view-settingsandendpoint-permission-declarationspass. - Unit:
buildViewFiltersAndSortsUpsertFlatOperations(create / update / delete, omitted kinds untouched, clearing a filter's group, unchanged root group not rewritten),inheritScopeViewOwnerVisibility. - Integration
view-field-relation-target: saving and clearing a lookup throughupsertViewFieldWithScope, and rejecting a relation target there.
Generated by Claude Code