feat(react-bindings): add legacy client sdk support #30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add Legacy Client Support to React Bindings SDK
Problem:
Currently, it's not possible to use the legacy client with the React Bindings SDK because the bootstrap initialisation always calls dataAdapter.setData(). However, Cloudflare integration requires using dataAdapter.setDataLegacy() method from the legacy Node SDK.
Solution:
Context:
Per discussion with Statsig: "I chatted with our SDK PM and they're still figuring out what the long-term plan will be for a server SDK on cloudflare. If they can get the new SDK running there it might be that, but for now the 'Legacy' Node SDK will be fully supported for cases like that, until we have a new solution."
This change enables developers using Cloudflare deployments to leverage the React bindings with the legacy Node SDK until a permanent solution is available.