@@ -190,10 +190,13 @@ Create a clearer single source of truth for CRM-driven bilingual display behavio
|
||||
|
||||
#### Current Maturity
|
||||
|
||||
- characterized
|
||||
- repeated dominant pattern identified
|
||||
- several partial abstractions already present
|
||||
- suitable for incremental implementation
|
||||
- completed
|
||||
- shared resolver introduced
|
||||
- helper test coverage added
|
||||
- helper contract verified and corrected
|
||||
- compatible consumers adopted across admin, search, My Portal, and summary types
|
||||
- stale JSONPath import cleanup completed where safe
|
||||
- behaviour-preserving migration completed
|
||||
|
||||
#### Implementation Strategy
|
||||
|
||||
@@ -202,6 +205,34 @@ Create a clearer single source of truth for CRM-driven bilingual display behavio
|
||||
- adopt first in bounded, read-only display families
|
||||
- preserve current fallback behaviour per consumer unless an explicit standardization decision is approved
|
||||
|
||||
#### Status
|
||||
|
||||
Completed.
|
||||
|
||||
Delivered in this workstream:
|
||||
|
||||
- shared resolver introduced
|
||||
- helper test coverage
|
||||
- helper contract verified and corrected
|
||||
- adoption across:
|
||||
- admin
|
||||
- search
|
||||
- My Portal
|
||||
- summary types
|
||||
- stale JSONPath import cleanup
|
||||
- behaviour-preserving migration
|
||||
|
||||
Remaining JSONPath usage in adopted areas is intentional where it falls outside the helper boundary.
|
||||
|
||||
That includes concerns such as:
|
||||
|
||||
- keyed lookup translation
|
||||
- project-type list translation
|
||||
- hyperlink / website rendering
|
||||
- mixed presentation rows
|
||||
- lifecycle / status / post-decision interpretation
|
||||
- other presentation-specific derived values
|
||||
|
||||
#### Expected Maintenance Benefit
|
||||
|
||||
- reduced duplication of display-resolution logic
|
||||
|
||||
Reference in New Issue
Block a user