Skip to content

GO-7578 Give hidden internal properties no display name - #16

Merged
requilence merged 1 commit into
mainfrom
go-7578-internal-property-names
Oct 9, 2026
Merged

requilence merged 1 commit into
mainfrom
go-7578-internal-property-names

Conversation

@requilence

Copy link
Copy Markdown
Contributor

Problem

The bundled name table maps the display name of every bundled relation to its key, including hidden internal ones. So a caller's own "Score" property resolved to the fulltext _score, and every write naming it was then refused as internal (API v2 / MCP eval, MCP-08). 67 of the 81 internal keys answered to a name, among them "Timestamp", "Snippet", "Mentions", "Highlighted" and "Sync status".

Change

  • A key that is both internal (InternalPropertyKeys) and hidden claims no name. It is written under its stored key, which still resolves back, so the reverse table stays an exact inverse. The name is free for a caller's own property.
  • Visible internal keys ("Created by", "Links") and id/type keep their names. For those, the refusal that explains the key is the useful answer.
  • The authoring schema still bans the old names of the three authoring-denied hidden keys ("Internal flags", "Order id", "Featured properties"). This follows the existing pattern for unresolved banned spellings.

Tests

  • New TestBundledNames_HiddenInternalKeysAnswerToNoName.
  • TestAuthoringDeniedKeysAreRefusedUnderEverySpelling adjusted for keys that have no name.
  • go test ./... passes.

Heart counterpart: anyproto/anytype-heart (GO-7578).

A caller's "Score" bound to the fulltext `_score`, and every write naming
it was then refused as internal. A key that is internal and hidden now
claims no name: it spells its stored key, which still resolves, and the
name is free for a caller's own property. Visible internal keys and
id/type keep their names, where the refusal is the useful answer.
@requilence
requilence merged commit 7a34818 into main Oct 9, 2026
2 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 9, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant