Todd Baert

@jeandreidc Great work! Thanks a lot. There's only 3 small things blocking my approval: - consider[ this comment ](https://github.com/open-feature/dotnet-sdk-contrib/pull/285#discussion_r1788077567)regarding error evals - [ can we build the rest client instead...

The flagd: add flag metadata (https://github.com/open-feature/js-sdk-contrib/issues/1151) ([b1c6d23](https://github.com/open-feature/js-sdk-contrib/commit/b1c6d235565f6cce02519d7c08bb6ad2dd791332)) note is a bit innaccurate - it was just a test that was added in flagd.

Hey @sahidvelji ! Thanks for opening this. I was dealing with various CI issues today so I didn't have time to go through it, but I'll give it some thought...

My notes, addressing each of @sahidvelji 's points: 1. I'm in favor of the possibility of supporting generics for the _object_ evaluation, and there's a few "data" objects that also...

@beeme1mr I'd like to get feedback from the rest of the TC first cc @kinyoklion @lukas-reining @thomaspoignant . If majority of us are in favor, I will basically convert this...

@kinyoklion WRT breaking changes, my impression based on what's been proposed is that consumers would be able to absorb the proposed changes relatively easily, it would entail changes such as:...

I think we can proceed as described. If it's alright with you @sahidvelji , I will proceed by basically turning each of these points into a child issue of this...

I've converted every point to it's own sub-issue, and labelled them with `v2`. You can see them all with this query: https://github.com/open-feature/go-sdk/issues?q=is%3Aissue%20state%3Aopen%20label%3Av2 You can also see another label (`needs discussion`)...

> Should we also replace all of `go-logr` with `slog` from the standard library as well? Almost certainly.

@beeme1mr should we wait for https://github.com/open-feature/go-sdk/issues/364 before we release?