Atomic composables + manager rewrite
Auto-generated from the source archive. Do not edit by hand — rerun
catalyst-changelog-syncinstead.
What changed
Section titled “What changed”- (Breaking)
grid-select-multiple-elementsis now a many-to-many manager. The Apply/Cancel batch contract is gone — the component renders the linked outer table plus a candidate dialog and emitslinkRequested(ids[])/unlinkRequested(ids[])immediately. - New atomic layer under
@aurora/composables/{atoms,presets}/: 9 data-table atoms (useTableSearch,useTableSort,useTablePagination,useTableSelection, …), 10 graphql atoms, and presetsusePaginatedDataTable,useStaticDataTable,usePivotMembership,useRelationshipPivot. - Three new fetchers (
mutateInsert,mutateDeleteByKeys,mutateDelete) and a new reusablegrid-pick-dialogcomponent for server-paginated single or multi pick.
Why it matters
Section titled “Why it matters”The brain layer (composables) now matches the visual layer’s atomic philosophy: single-responsibility lego bricks plus opinionated presets for the common server-paginated list. Migration path for the breaking item: any consumer of <au-grid-select-multiple-elements> must drop the previous [value] / (valueChange) Apply/Cancel wiring and instead handle (linkRequested) and (unlinkRequested) to mutate the pivot and refresh linkedData. Imports through the @aurora alias root keep resolving — only that component’s I/O contract changed.