Emiliano Sanchez

Hi @besh , Thank you for your suggestion and draft PR. We will take it into account, but we cannot prioritize that work at the moment. For your information, we...

Hi @besh > Is it work you'd like to prioritize in the future? I certainly don't mind finalizing my PR and prepping it for then. Yes, we will prioritize it...

Hi @tjosepo , You are right. When `SplitFactoryProvider` is called with the `config` prop, rather than the `factory` prop, the `client` is null on the first render. This was done...

For the record, we have released [v2 of the React SDK](https://github.com/splitio/react-client/blob/master/MIGRATION-GUIDE.md#migrating-to-react-sdk-v200), and the `SplitFactoryProvider` now makes the Split factory and client objects available from the initial render if you pass...

Yes @jamesarosen , As explained [here](https://github.com/splitio/vercel-integration-utils/issues/16#issuecomment-2260933747), this package doesn't support custom storages yet :/. Because of the benefits you mentioned, we plan to support it, but there is no ETA...

Hi @neriyarden, Yes, that behavior (`client` is `null` when `isReady` is still `false`) is expected for the `SplitFactoryProvider` component. This is a breaking change compared to the now deprecated `SplitFactory`...

Hi @neriyarden, We have released [v2 of the React SDK](https://github.com/splitio/react-client/blob/master/MIGRATION-GUIDE.md#migrating-to-react-sdk-v200). In this version, the `SplitFactoryProvider` component makes the `factory` and `client` objects available from the initial render, so you should...

Hi @jordan-lantz, Thank you for your feedback. We will take your suggestions into account when updating the public documentation. Regarding the proposed updates (renaming the environment variables and revisiting their...

Hi @ewdicus , The issue you encountered is likely related to a breaking change introduced in version 2.0.0. The new `useSplitClient` and `useSplitTreatments` hooks, which replace the now removed `useClient`...

You are welcome @ewdicus > Thanks for the quick response! Setting updateOnSdkUpdate on the client does change that to the previous behavior. However, I also have to set it on...