Context
Found while reviewing neomjs/neo#20276, the sorting fix for #20275. The probe ran the engine's own unit setup against dev (3ed29de673) and against #20276's head (59e702372f). Both give the same rows. The filter is {operator: '>=', property, value: 30} over two items scoring 20 (id 1) and 50 (id 2), so every row should keep [2]:
property owner kept expected
tp (flat; the probe's control) Collection, Store R/T [2] [2]
stats.score (path into Object) Collection [] [2]
stats.score (path into Object) Store, Records [] [2]
stats.score (path into Object) Store, Turbo [] [2]
user.score (declared nested) Store, Records [2] [2]
user.score (declared nested) Store, Turbo [] [2]
R = autoInitRecords: true, T = autoInitRecords: false (Turbo Mode).
The Problem
A filter whose property is a dotted path keeps nothing unless the item itself exposes that dotted key. Only a Record with a declared nested field does. Turbo Mode stores, plain items in a Collection, and paths into Object fields filter out every item. The grid header's inline filter takes the column's dataField as its property. A dotted column in a Turbo Mode grid therefore filters out every row. After #20276, sorting resolves these paths, but filtering still reads the key directly.
The Architectural Reality
Neo.collection.Filter#decide reads recordValue = item[property] (src/collection/Filter.mjs). Every operator uses that one direct read, typedIncluded and its typedKeys set included.
Neo.data.Record#get(field) resolves an undeclared dotted path through Neo.ns(field, false, this[dataSymbol]) (src/data/RecordFactory.mjs). A declared nested field exposes its dotted getter (record['address.city'], learn/guides/datahandling/Records.md).
grid/header/Button.mjs builds its inline filter as store.getFilter(me.dataField, 'header-inline').
- #20276 adds
Neo.collection.Sorter.getValue(item, property). It reads the key directly first, then, for a dotted string path whose value is undefined, tries item.get(path) and then Neo.ns(path, false, item). The same PR makes Store#resolveField hydrate the declared root of an undeclared dotted path in Turbo Mode without stamping the dotted key.
- Design authority:
learn/guides/datahandling/Grids.md configures columns with dotted dataFields ({text: 'Firstname', dataField: 'user.firstname'}). The header filter takes that dataField as its property, and #20275 treats a dotted property that sorts as a no-op as a bug.
The Fix
Filter#decide reads recordValue through the resolver sorting uses after #20276: Neo.collection.Sorter.getValue(item, property), or a neutral static that both classes import if review prefers that. Flat properties keep their one-read fast path. The dotted fallback runs only when the direct read is undefined.
Acceptance Criteria
Out of Scope
- Sorting by dotted paths: #20275, PR #20276.
- Remote filtering, which the server applies.
Related
#20275 (sorting, same resolution rule) · PR #20276 (the resolver this builds on) · examples/grid/nestedRecordFields.
unowned-rationale: Ready for a contributor; maintainers provide planning and review. It starts once #20276 merges, since that PR carries the resolver.
Live latest-open + closed sweep: checked the latest 20 open issues plus closed searches ("filter dotted path", "filter nested field property"; no same-surface hit) at 2026-11-04T19:35Z. No equivalent or prior exclusion found. A2A sweep (last 30, all read-states): no claim on this scope. Memory Core sweep: earlier soft-hydration work covered calculated fields in Turbo filtering, not dotted paths. Own-assignment sweep: no same-surface ticket.
Retrieval Hint: "Filter dotted property path never matches Turbo Mode raw items or undeclared Object field paths"
Origin Session ID: 2171b2cd-e447-4cac-8b9f-ccadc6e20db5
Context
Found while reviewing neomjs/neo#20276, the sorting fix for #20275. The probe ran the engine's own unit setup against
dev(3ed29de673) and against #20276's head (59e702372f). Both give the same rows. The filter is{operator: '>=', property, value: 30}over two items scoring 20 (id 1) and 50 (id 2), so every row should keep[2]:R =
autoInitRecords: true, T =autoInitRecords: false(Turbo Mode).The Problem
A filter whose
propertyis a dotted path keeps nothing unless the item itself exposes that dotted key. Only a Record with a declared nested field does. Turbo Mode stores, plain items in aCollection, and paths intoObjectfields filter out every item. The grid header's inline filter takes the column'sdataFieldas its property. A dotted column in a Turbo Mode grid therefore filters out every row. After #20276, sorting resolves these paths, but filtering still reads the key directly.The Architectural Reality
Neo.collection.Filter#decidereadsrecordValue = item[property](src/collection/Filter.mjs). Every operator uses that one direct read,typedIncludedand itstypedKeysset included.Neo.data.Record#get(field)resolves an undeclared dotted path throughNeo.ns(field, false, this[dataSymbol])(src/data/RecordFactory.mjs). A declared nested field exposes its dotted getter (record['address.city'],learn/guides/datahandling/Records.md).grid/header/Button.mjsbuilds its inline filter asstore.getFilter(me.dataField, 'header-inline').Neo.collection.Sorter.getValue(item, property). It reads the key directly first, then, for a dotted string path whose value isundefined, triesitem.get(path)and thenNeo.ns(path, false, item). The same PR makesStore#resolveFieldhydrate the declared root of an undeclared dotted path in Turbo Mode without stamping the dotted key.learn/guides/datahandling/Grids.mdconfigures columns with dotteddataFields ({text: 'Firstname', dataField: 'user.firstname'}). The header filter takes thatdataFieldas its property, and #20275 treats a dottedpropertythat sorts as a no-op as a bug.The Fix
Filter#decidereadsrecordValuethrough the resolver sorting uses after #20276:Neo.collection.Sorter.getValue(item, property), or a neutral static that both classes import if review prefers that. Flat properties keep their one-read fast path. The dotted fallback runs only when the direct read isundefined.Acceptance Criteria
Collectionand raw items in a Turbo ModeStoreandTreeStore: the table's empty rows keep[2]. Flat-property filters are unchanged.user.scorekeeps[2]in both).devbefore the fix:test/playwright/unit/collection/forFilter,test/playwright/unit/data/forStoreandTreeStore. The existing suites pass.Out of Scope
Related
#20275 (sorting, same resolution rule) · PR #20276 (the resolver this builds on) ·
examples/grid/nestedRecordFields.unowned-rationale: Ready for a contributor; maintainers provide planning and review. It starts once #20276 merges, since that PR carries the resolver.
Live latest-open + closed sweep: checked the latest 20 open issues plus closed searches ("filter dotted path", "filter nested field property"; no same-surface hit) at 2026-11-04T19:35Z. No equivalent or prior exclusion found. A2A sweep (last 30, all read-states): no claim on this scope. Memory Core sweep: earlier soft-hydration work covered calculated fields in Turbo filtering, not dotted paths. Own-assignment sweep: no same-surface ticket.
Retrieval Hint: "Filter dotted property path never matches Turbo Mode raw items or undeclared Object field paths"
Origin Session ID: 2171b2cd-e447-4cac-8b9f-ccadc6e20db5