Christie Williams

@allicanseenow > right now if `ldClient?.identify` is called, there is no way to observe whether the user object has changed You're right, though [LDClient#identify](https://launchdarkly.github.io/js-client-sdk/interfaces/_launchdarkly_js_client_sdk_.ldclient.html#identify) returns a promise that resolves (or...

An alternative to using `useFlags` would be to use the `useLDClient` hook - it will return `undefined` until the client is ready. For example, an "is ready" custom hook might...

Agreed that this would be a nice addition, it's something we've talked about. There's something similar in the [Vue SDK](https://launchdarkly.github.io/vue-client-sdk/index.html#useLDFlag). Will let you know when we've committed to it. Thanks...

That may be expected behavior. Note that the documentation says: > the React SDK will only subscribe for updates to these flags I think what you're seeing in the network...

This was fixed in [2.27.0](https://github.com/launchdarkly/react-client-sdk/releases/tag/2.27.0), check it out and let me know if you're still having problems.

@wyattanderson: > I agree with the suggestion here that sendEventsOnlyForVariation should be the default. Me too. > Perhaps it's an oversight, but this seems to completely undermine core LaunchDarkly product...

A fix for this went out in [2.27.0](https://github.com/launchdarkly/react-client-sdk/releases/tag/2.27.0), take a look and see if it's working more as expected now.