finding(plugin-map): the legacy filter.map warning names a default name title field that objectui#5953 removed #8270

Found while compiling packages/plugin-map/README.md's snippets for objectui#5174 (batch 35). Filed unassigned and NOT touched there — that batch may not edit packages/plugin-map/src/**.

What

warnOnLegacyFilterMapConfig() in packages/plugin-map/src/ObjectMap.tsx warns when a map's configuration is stashed under the legacy filter.map shape (objectui#4034). Its message tells the reader which field names the map fell back to:

filter.map is no longer read as map configuration, so this map is rendering with the DEFAULT field names (latitude / longitude / name).

Those are not the defaults. getMapConfig()'s default branch, in the same file, returns:

• latitudeField: 'latitude'
• longitudeField: 'longitude'
• locationField: 'location'
• descriptionField: 'description'
• no titleField at all, deliberately, with an eight-line comment citing objectui#5953: a forged 'name' binding outranks the object's own declared nameField at step 0 of getRecordDisplayName, so an ABSENT binding must stay absent and let that resolver decide.

So the warning names one default that objectui#5953 removed on purpose (name), and omits two that exist (location, description).

Why it matters

This is the diagnostic a reader gets at exactly the moment they are confused about which field names the map is reading — the message exists because the alternative was "dropping the author's markers without a trace". Sending them to look for a name field is the one wrong answer that shape of confusion can produce: the map falls back to location (which the message never mentions), and the marker TITLE comes from the record-title precedence, not from any field name at all.

It also reads as a claim about the code that is now false, next to a comment block in the same file that explains at length why it is false — so the next reader has to work out which of the two to believe.

Reachability

Dev-mode only (isDev() guard), warn-once per distinct schema. Nothing renders differently; the cost is entirely in what the message teaches. Not a runtime defect.

Suggested repair

One string. Restate the branch the code actually takes: latitude / longitude / location / description, and say that the marker title is resolved by getRecordDisplayName rather than by a default field name. packages/plugin-map/README.md already documents it that way (the "The map block" section), so the README and the warning would then agree.

Refs: objectui#5174, objectui#4034, objectui#5953.

Filed by an os-dev agent seat while working objectui#5174 batch 35; session reference session_01FhBNJcLRZLe8M87VcUgpKr.

Generated by Claude Code