[sameerank]

Summary

This PR contains documentation and regression-test changes only. The browser provider implementation is introduced in #336, while the supported getPrecomputedContext(configuration) accessor is provided by #344 through its merge of #353.

• document static offline initialization with a supported copy of the precomputed context
• use getPrecomputedContext(configuration) instead of inspecting the opaque wire or parsed configuration
• load configuration with setConfiguration() before registering the provider
• register the provider and matching context together with OpenFeature.setProviderAndWait(provider, context)
• treat {} and contexts containing only undefined values literally
• preserve INVALID_CONTEXT behavior for context-specific precomputed snapshots that do not match
• add lifecycle coverage for initialization, context clearing, error transitions, and recovery
• use the root browser entry point for precomputed configuration and /rules-based for dynamic-context rules

Why

A context-specific precomputed configuration is a snapshot for the context used to generate it. The effective OpenFeature context must match so provider hooks and Datadog tracking observe the same subject used for evaluation.

The configuration wire and parsed configuration are opaque contracts. getPrecomputedContext(configuration) lets consumers obtain a detached copy without inspecting internal fields.

An empty OpenFeature context is a real context. It does not mean “restore the embedded context.” Clearing context therefore supplies {} and puts a context-specific precomputed-only provider into ERROR until the matching context is set again.

Behavior

• construct DatadogOfflineProvider, then load configuration with setConfiguration()
• loading configuration before registration does not validate against a placeholder context
• registration validates against the actual OpenFeature context
• matching precomputed configuration evaluates locally
• context-agnostic precomputed configuration continues to work with any context
• {}, { targetingKey: undefined }, and cleared global context are treated literally
• mismatching context returns coded defaults with INVALID_CONTEXT
• setting the matching context recovers the provider to READY
• rules-based offline evaluation continues to support dynamic contexts without fetching

Dependency and merge order

This PR is stacked on #336.

1. Merge [FFL-2835] Parse flags configuration wire format #344 into main.
2. Retarget and merge FFL-2753 Add browser DatadogOfflineProvider #336 into main.
3. Retarget this PR to main and merge it.

PR #349 adds opt-in exposure, evaluation, and RUM tracking parity to DatadogOfflineProvider. PR #351 adds explicit precomputed and rules-based configuration fetchers; both are independent follow-ups.

Jira: https://datadoghq.atlassian.net/browse/FFL-2871

Validation

• full browser suite passed: 16 suites and 203 tests
• browser production build passed
• browser TypeScript checks passed
• Biome and Prettier checks passed
• final PR diff is limited to the browser README and offline-provider regression tests

[leoromanovsky]

👍

[BenoitZugmeyer]

thought: When seeing this, I was surprised why it cannot be simplified as:

await OpenFeature.setProviderAndWait(provider, getPrecomputedContext(configuration))

I understand now this is to work around OpenFeature typings, where context is not optional, but it is definitely surprising. Maybe a PR upstream could help simplifying this!

[sameerank]

Yep that’s why the conditional is needed. getPrecomputedContext() returns EvaluationContext | undefined, while the OpenFeature overload accepts either no second argument or a defined EvaluationContext.

We also cannot substitute {} for undefined, because this provider treats {} as an explicitly selected empty context. I agree an upstream typing/API change could make this simpler. The fix I'm imagining would live in the OpenFeature code though. Specifically here and here would let context be optional

setProviderAndWait(provider: Provider, context?: EvaluationContext): Promise<void>

setProviderAndWait(
  domain: string,
  provider: Provider,
  context?: EvaluationContext
): Promise<void>