@@ -148,6 +148,27 @@ The adoption target should be explicit, such as:
|
||||
|
||||
Do not attempt mass adoption by default.
|
||||
|
||||
### CRM Display Infrastructure Rule
|
||||
|
||||
When rendering a standard CRM formatted/display value:
|
||||
|
||||
- `resolveCrmDisplayValue(...)` should be used.
|
||||
|
||||
Developers should not introduce new inline JSONPath lookups for the standard CRM formatted/display-value translation pattern.
|
||||
|
||||
If the translation concern does not match the helper boundary, it should be treated as a separate abstraction rather than extending the helper.
|
||||
|
||||
This includes concerns such as:
|
||||
|
||||
- keyed lookup translation
|
||||
- list translation
|
||||
- hyperlink / website rendering
|
||||
- mixed presentation rows
|
||||
- lifecycle interpretation
|
||||
- status interpretation
|
||||
- post-decision interpretation
|
||||
- other derived presentation values
|
||||
|
||||
---
|
||||
|
||||
## 4. Branching Governance
|
||||
|
||||
Reference in New Issue
Block a user