Localize semantic error presentation - #382
Conversation
|
To preview the documentation for this pull request, visit the following URL:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #382 +/- ##
===========================================
+ Coverage 90.94% 92.79% +1.84%
===========================================
Files 135 651 +516
Lines 6251 17039 +10788
Branches 1338 4354 +3016
===========================================
+ Hits 5685 15811 +10126
- Misses 172 482 +310
- Partials 394 746 +352
🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Current status: Overall coverage is partial; this snapshot does not prove that all of its findings are resolved.
Last reconciled onbdcd085. See aggregate Bugbot status.
🤖 Bugbot review snapshot
Bugbot reported 1 potential problem when commit 84a8d7d was analyzed. This snapshot is historical; use the status block above for current state. 1 finding is linked to changed code.
Findings
- medium: Preserve per-error recovery context —
src/application/policies/application_error_presentation_policy.ts:22
Bugbot: review incomplete
Incomplete coverage
|
84a8d7d to
bdcd085
Compare
Semantic application errors now use validated recovery descriptors and centralized locale-aware catalogs, so GitHub Action and local CLI failures present consistent English or Spanish guidance while preserving stable codes and references. Error publication is consolidated at the completion boundaries and generated artifacts and documentation are updated accordingly.
What changed
Review notes
ApplicationErrormust use the typedrecoverydescriptor; arbitraryimpact,action, andretainedStateoverrides are no longer part of the semantic error options.