This message was deleted.

So far we've used growthbook with react and go. Both have been written in quite broken ways. It seems like there was little understanding of the way Go and React work

Hi James, thanks for the feedback. Happy to meet to talk through your use case and see how we can improve the SDKs. •

growthbook.setFeatures

and

growthbook.setAttributes

should cause the GrowthBookProvider to re-render. The context value doesn't change, but the Provider has an internal state that gets updated that should trigger a re-render. If that's not happening, it may be a bug that we can look into. •

growthbook.subscribe

is an internal method with a very niche use case. I agree the naming isn't great there - one of the reasons we haven't added it our documentation.

Ah I see, we did see the

setRenderer

thing (which we thought would be something we had to implement against), but thought in practice it probably wouldn't be the best approach I would note that it won't work if you use the growthbook instance with multiple providers - might be worth making it subscription based, and then cases like ours can leverage that too