valtech-components 4.0.990 → 4.0.991
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/esm2022/lib/services/errors/error-logging.interceptor.mjs +30 -5
- package/esm2022/lib/version.mjs +2 -2
- package/fesm2022/valtech-components.mjs +30 -5
- package/fesm2022/valtech-components.mjs.map +1 -1
- package/lib/services/errors/error-logging.interceptor.d.ts +9 -1
- package/lib/version.d.ts +1 -1
- package/package.json +1 -1
|
@@ -16,7 +16,15 @@ export declare const EXPECTED_NOT_FOUND: HttpContextToken<boolean>;
|
|
|
16
16
|
* Interceptor HTTP de observabilidad (Capa 1 del estándar de manejo de errores).
|
|
17
17
|
*
|
|
18
18
|
* Para CADA respuesta HTTP con error:
|
|
19
|
-
*
|
|
19
|
+
* 0. Si es un GET (idempotente) que falló con 502/503/504, reintenta hasta 2
|
|
20
|
+
* veces con un backoff corto (400ms/800ms) ANTES de pasar al resto del
|
|
21
|
+
* pipeline — el caso típico es un cold-start de Lambda en dev: 3-4
|
|
22
|
+
* requests en paralelo al bootstrap (auth/profile + runs + org/{id})
|
|
23
|
+
* pegan contra lambdas frías al mismo tiempo, todas 504, y ~2s después ya
|
|
24
|
+
* están tibias y funcionan. Detectado en Merotz dev 2026-08-17. Nunca
|
|
25
|
+
* reintenta POST/PUT/DELETE/PATCH (no son idempotentes) ni 4xx (error de
|
|
26
|
+
* negocio, reintentar no lo arregla).
|
|
27
|
+
* 1. Si sigue fallando tras los reintentos: normaliza el error con `interpretError`.
|
|
20
28
|
* 2. Loguea un evento estructurado a consola con el prefijo `[HTTP]`.
|
|
21
29
|
* 3. Reporta el error a Firebase Analytics (`source: 'http'`), si hay analytics.
|
|
22
30
|
*
|
package/lib/version.d.ts
CHANGED