Todd Baert

Ya, this seems like an improvement compared with what we already have which mixes conceptual and practical dev docs.

I wonder if we should add this to the spec as well?

> I've not implemented these two requirements > > [Requirement 3.2.2.3](https://openfeature.dev/specification/sections/evaluation-context#conditional-requirement-3223): The API MUST have a method for setting evaluation context for a domain. > [Requirement 3.2.2.4](https://openfeature.dev/specification/sections/evaluation-context#conditional-requirement-3224): The API MUST...

> > Approved. Agree with your deprecation suggestion @Kavindu-Dodan > > Unfortunately this was not straightforward. We used same `Metadata` interface for both clients and providers. Given that domains are...

@jhollanderpax8 I think part of the issue here is we are missing some Javadoc. We also are missing a very specific test for setting global context (it's covered, but only...

@gunishmatta here's the implementation I did in the JS SDK: https://github.com/open-feature/js-sdk/pull/795. You can disregard the `RECONCILING` stuff - that only applies to client-side SDKs, which Java is not. The relevant...

Unassigned due to inactivity.

I think this is done with https://github.com/open-feature/java-sdk/pull/1096. I will confirm and close in the next couple days.

I think `Number` makes sense. If we add it though, what do we do with providers that don't specifically implement this? Or would we even expect them to? Might we...

I like your plan. I'm really not sure about your question though. My gut says deprecate the other numerics, but I'm not sure. 🤔