[Feature] Consider exposing TargetingKey with all value exporters

[Kavindu-Dodan]

Consider ImmutableStructure.asMap() ¹ or ImmutableStructure. asObjectMap() ² methods. These expose the attributes but they do not include the targeting key ³.

This could lead to unexpected behaviors where evaluations miss targeting key if provider authors overlook the implementation details (see ⁴). In contrast, go-sdk perform a context flattening to include targeting key ⁵ and js-sdk context is a record hence this issue does not exist in them.

AC

If agreed, we should include the targeting key in bulk exporters (ex:- ctx.asObject) as well as improve overall context handling by documentation improvements

Footnotes

1. https://github.com/open-feature/java-sdk/blob/v1.7.3/src/main/java/dev/openfeature/sdk/MutableStructure.java#L90 ↩

2. https://github.com/open-feature/java-sdk/blob/v1.7.3/src/main/java/dev/openfeature/sdk/AbstractStructure.java#L25 ↩

3. https://github.com/open-feature/java-sdk/blob/v1.7.3/src/main/java/dev/openfeature/sdk/ImmutableContext.java#L21 ↩

4. https://github.com/open-feature/java-sdk-contrib/pull/676 ↩

5. https://github.com/open-feature/go-sdk/blob/main/openfeature/client.go#L687-L695 ↩