You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by samuelstroschein February 18, 2024
Problem
Referencing the same message in multiple places leads to a broken message.
No guarantee exists that a message with the content like "learn more" won't be changed by someone to "learn more about unlimited inboxes". If the message is rendering all "learn more" references, the example website below will break at 2 and 3.
Proposal
A lint rule that detects if a message id is used multiple times in source code.
// unlimited inboxes<p>{m.elephant_big_tree()}</p>// manage team members// 💥 error m.elephant is used multiple times<p>{m.elephant_big_tree()}</p>
// spam report// 💥 error m.elephant is used multiple times<p>{m.blue_box({title: m.elephant_big_tree()})}</p>
(Creating new messages is cheaper than trying to manage shared messages.)
Discussed in opral/monorepo#2253
Originally posted by samuelstroschein February 18, 2024
Problem
Referencing the same message in multiple places leads to a broken message.
No guarantee exists that a message with the content like "learn more" won't be changed by someone to "learn more about unlimited inboxes". If the message is rendering all "learn more" references, the example website below will break at 2 and 3.
Proposal
A lint rule that detects if a message id is used multiple times in source code.
(Creating new messages is cheaper than trying to manage shared messages.)
Additional information
The text was updated successfully, but these errors were encountered: