feat(openfeature): expose dynamic offline rules (FFL-2837 PR3)

[btthomas]

Pull request stack

1. Plan PR (#1345)
2. PR1: Rules engine boundary (#1346)
3. PR2: Dynamic offline evaluation (#1347)
4. PR3: Provider API and documentation (feat(openfeature): expose dynamic offline rules (FFL-2837 PR3) #1348) <- you are here

This description uses Simplified Technical English. Technical names and API names do not change.

Summary

This PR exposes dynamic offline rules through the existing offline provider.

• The offline provider passes every effective OpenFeature context to FlagsClient.
• The provider treats {} as a real context.
• clearContext() does not restore a context from the configuration.
• A missing targeting key stays missing.
• Rules configurations stay ready after context changes.
• Context changes do not fetch configurations.
• Configuration parse failures produce provider errors.
• Recovery emits Ready before ConfigurationChanged.
• Integration tests cover rules, mixed data, parse errors, recovery, and missing targeting keys.
• The README explains precomputed, rules, and mixed configurations.
• Both example applications include a rules-context switch.

Reason

The provider lifecycle already supports offline configuration and context changes. The provider passes the current resolution context and logger to the core rules path. A new provider class is not required.

OpenFeature supplies {} for an unset or cleared global context. The provider cannot distinguish this state from an explicit {}. Therefore, it passes {} literally. For a context-specific precomputed configuration, the application explicitly sets the context returned by getPrecomputedContext(configuration).

OpenFeature hook constraint

Web SDK 1.8 freezes the hook context before it calls before hooks. It does not accept a replacement context from a hook. This PR does not claim that a hook can replace one resolution context.

Temporary upstream code

This PR adds three fixture TODO(FFL-2837) markers. The complete stacked branch contains 19 markers. PR1 and PR2 contain the other 16 markers.

The three PR3 fixtures use the legacy rulesBased JSON wire. Replace them with one canonical version 1 rules.response base64 fixture after a published flagging-core release contains openfeature-js-client#344 through 939da97 and the required SHA digest validation follow-up.

Commits ab22ad0 and 939da97 only refresh generated Node-server declarations and isolate browser provider tests. They do not change the fixture or runtime contract. PR #336 is currently at 6d3d6a4 and adds no new logical behavior in its latest restack.

User impact

A customer can load one rules configuration and call OpenFeature.setContext for new subjects. The provider evaluates each context locally. It does not fetch assignments.

A precomputed customer must explicitly set the matching OpenFeature context. An empty context does not select the embedded configuration context.

Matching precomputed data has priority when both branches exist. Keep the original wire when it contains rules because the temporary serializer cannot recreate the protobuf payload.

Remaining gates

• Publish and pin the flagging-core release that contains PR Add Support for RN 0.71 #344.
• Publish and consume the shared helper from PR Tap interactions not reported after project setup on IOS #353.
• Replace the three legacy fixture branches.
• Define the regular-expression, salt, size, and security policies.
• Run the packed dependency and rules flow in Hermes and JSC.

This PR remains a draft until these gates are complete.

Checks

• Core and React Native type checks
• Targeted ESLint and formatting checks
• 11 targeted Jest suites
• 175 targeted tests
• git diff --check

[sameerank]

This converts an empty effective OpenFeature context ({}) to undefined, causing FlagsClient to reuse its stored/embedded context, and this is being removed in #1359, right?

[datadog-prod-us1-5]

 

✨ Unblock PR with BitsAI

⚠️ Warnings

🚦 1 Pipeline job failed

DataDog/dd-sdk-reactnative | test:native-ios-newarch     

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: c261929 | Docs | Datadog PR Page | Give us feedback!}