Skip to content

[finding] common.search has zero readers repo-wide after PR #4391 — retire from the ten packs, or keep as vocabulary? #4392

Description

@yinlianghui

Recorded by the PM seat from PR #4391's risk list (the #4375+#4376 pair), filed so the decision isn't lost. Filed unassigned.

Fact

PR #4391 moved LookupField.tsx's placeholder from the t('common.search') + '...' concatenation to the reused table.search key. LookupField was common.search's only consumer, so the key now has zero readers repo-wide while existing in all ten locale packs.

The decision this card holds

Retiring a key from ten packs is a real decision with key-parity consequences (all ten must drop it together, and any dormant defaults-map copies must go with it), and PR #4391 correctly left it out of scope. Options:

Verify the zero-reader premise at claim time (git grep -n "common.search" -- packages apps examples), since call sites move.

Related: PR #4391 (where the last reader left), #4375 (the concatenation card), #4328 (the dead-surface discipline precedent).

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions