Skip to content

Commit e9e0ec7

Browse files
committed
chore(changeset): declare Metadata-protocol: none for the record-title wording fix
Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01D6F9axfoPzR7t8G1J7Ytzz
1 parent 55f0dba commit e9e0ec7

1 file changed

Lines changed: 1 addition & 0 deletions

File tree

‎.changeset/25071-composite-title-stored.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@
55
fix(lint): the record-title diagnostics no longer steer a composite title that must be queried into a formula field
66

77
Clause-②: no (wording only: no verdict, severity, code, key or export moves)
8+
Metadata-protocol: none
89

910
The `title-format-retired` and `title-unresolvable` messages and fix lines, the `object/missing-name-field` fix line, and the `os explain title-format-retired` text now say the same thing: a composite record title that an import, a sort or a search must match is a stored computed field, a non-formula field (such as a `text` field) that declares an `expression`, which the engine computes and stores on every write, designated as `nameField`. A `formula` field with `returnType: 'text'` stays a legal `nameField` for a title shown for display only: its value is computed on read and stored nowhere, so a sort by it is refused, search never reaches it, and an import cannot match a lookup cell against it.
1011

0 commit comments

Comments
 (0)