@webpieces/rules-config 0.4.738 → 0.4.740

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@webpieces/rules-config",
3
- "version": "0.4.738",
3
+ "version": "0.4.740",
4
4
  "description": "Shared webpieces.config.json loader. Single source of truth for validation rule configuration consumed by @webpieces/ai-hook-rules, @webpieces/code-rules, and @webpieces/nx-webpieces-rules.",
5
5
  "type": "commonjs",
6
6
  "main": "./src/index.js",
@@ -671,8 +671,9 @@ external consumer. So:
671
671
  text as `HttpBadRequestError`'s `guiMessage`, which IS sent (as `guiAlertMessage`).
672
672
  - A client must branch on the error TYPE, on `subType`, on `errorCode` or on `guiAlertMessage` — never
673
673
  on the prose of `message`. Against a current webpieces server that prose is a constant per status.
674
- - An app that deliberately wants to publish richer text registers an `ErrorTranslation` with
675
- `ClientRegistry`; its `toWire()` result is sent verbatim. That is the explicit, greppable opt-out.
674
+ - An app that deliberately wants to publish richer text installs an `ErrorTranslators` on
675
+ `ClientRegistry` (`setErrorTranslators`); its `toWire()` response status, reason phrase, headers
676
+ and body — is sent verbatim. That is the explicit, greppable opt-out.
676
677
 
677
678
  ## How to Request Approval
678
679