Kavindu Dodanduwa

We currently maintain several getting started guides based on flagd [[1]](https://openfeature.dev/docs/category/getting-started). And this section contains examples that use GO Gin [[2]](https://openfeature.dev/docs/tutorials/getting-started/go) & Java spring boot [[3] ](https://openfeature.dev/docs/tutorials/getting-started/java). However, as others...

I also agree that this does not apply to dynamic-context usage. For static context, given context change is an important event, I am in favor of the _throw/indicate error_ approach....

> state diagram I like the state diagram as we can define the operation on the transition compared to flow chart.

@gunishmatta really nice work 🙌 could you please check the minor changes I proposed? They should be easy to complete and once done I think this is ready

@hairyhenderson thanks for this concern and I went through the slack conversation. To add some detail, we use the same approach in Java [1]. And I agree that testing becomes...

@evankanderson like in your proposal, a mock implementation of `IClient` should help you with testing code modules that depend on an OpenFeature client. The mock implementation could be as simple...

@hairyhenderson @evankanderson I opened https://github.com/open-feature/go-sdk/pull/268 to address some of the testing issues you faced. The fix focuses on introducing `IOFApi ` interface which includes most of the OpenFeatuer specification contracts...

I will close this as we now have test-friendly interfaces exposed from the SDK. This was done through https://github.com/open-feature/go-sdk/pull/268 and released with version [1.12.0](https://github.com/open-feature/go-sdk/releases/tag/v1.12.0)

@cndoit18 thank you for bringing this up. Currently, we use logr [1], and once we upgrade our Go version to 1.21, we could consider migrating/using the standard logger. I will...

Added breaking change tag as adoption of slog will break backward compatibility for older go versions. When implementing, we should consider interoperability with logr [1] and see if there're any...