@yuno-payments/dashboard-api-mfe 2.7.1 → 2.7.3

package/build/cjs/types/queries/feature-flags/index.test.d.ts

@@ -1,11 +1,10 @@
 /**
- * Tests for the FEATURE_FLAGS_PROVIDER kill-switch in feature-flags/index.ts.
+ * Tests for the feature-flags/index.ts routing.
  *
- * The switch resolves at module-load time, so each test isolates a fresh
- * module instance via `jest.isolateModules` after re-stubbing the env var.
- *
- * `require()` is used inside `isolateModules` because that API is the
- * synchronous CJS entry point Jest exposes for re-loading modules under
- * a mutated env. ESM `import()` would be evaluated asynchronously outside
- * the isolated scope and break the test contract.
+ * As of v2.7.2 the switch is hardcoded to datadog (see
+ * `src/utils/feature-flags-provider.ts`). The legacy hooks file is kept
+ * around for a one-revert rollback path but is no longer reachable from
+ * the public hooks. These tests cover both: the public entry always
+ * exposes the datadog impls, and both modules still share the same
+ * function shape so a future env-var-driven rollback would Just Work.
  */

package/build/cjs/types/utils/feature-flags-provider.d.ts

@@ -1,21 +1,21 @@
 /**
- * Feature-flag provider switch (kill-switch for DAS-15798 migration).
+ * Feature-flag provider switch (DAS-15798 migration).
  *
- * Set via the `FEATURE_FLAGS_PROVIDER` build env var (inlined at build
- * time by rspack DefinePlugin). Defaults to 'legacy' (the in-house Go
- * service via React Query). Flip to 'datadog' once the Datadog Feature
- * Flags integration is bootstrapped by container-mfe.
+ * Hardcoded to 'datadog' as of v2.7.2. The env-var-based switch
+ * (`FEATURE_FLAGS_PROVIDER`) is gone: api-mfe queries always route to
+ * `./datadog-hooks`, and `dashboard-container-mfe`'s bootstrap effect
+ * (which checks this function) always proceeds to set up the
+ * OpenFeature Datadog provider.
  *
- * Read by `src/queries/feature-flags/index.ts` to route hook consumers
- * between `./datadog-hooks` and `./legacy-hooks`. Also re-exported from
- * the package public API so `dashboard-container-mfe` can read the same
- * inlined value to gate its Datadog OpenFeature bootstrap — single
- * source of truth across both MFEs.
+ * The function and type are kept around (instead of inlining the
+ * constant) so:
+ *   1. Consumers like container-mfe don't need a code change.
+ *   2. Rollback to the legacy hooks (revert this file + republish) stays
+ *      a single-file change.
  *
- * Rollback path: flip the env var and rebuild/redeploy api-mfe
- * (~5–10 min). No code revert needed.
- *
- * Delete this file (and the legacy hooks branch) after Phase 4 soak.
+ * Once we're confident no rollback is needed, delete `./legacy-hooks`,
+ * delete this file, and inline the datadog branch in
+ * `queries/feature-flags/index.ts` (Phase 5 cleanup).
  */
 export type FeatureFlagsProvider = 'datadog' | 'legacy';
 export declare function getFeatureFlagsProvider(): FeatureFlagsProvider;

package/build/cjs/types/yuno-dashboard-api-mfe.d.ts

@@ -9,3 +9,4 @@ export * from './websockets';
 export * from './utils';
 export { getFeatureFlagsProvider, type FeatureFlagsProvider, } from './utils/feature-flags-provider';
 export { emitExpired, resetExpiredGuard, SESSION_EXPIRED_MESSAGE_TYPE, } from './lib/session-expired';
+export { OpenFeature } from '@openfeature/web-sdk';