fix(node-server-sdk): No FDv1 fallback when using custom datasystem #1088
+63
−70
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.
Requirements
Related issues
SDK-1802
Describe the solution you've provided
Note
Medium Risk
Touches core SDK data source construction and fallback behavior, which can affect flag delivery and initialization paths; changes are localized but could impact runtime update behavior if misconfigured.
Overview
Fixes FDv2 initialization so an FDv1 polling fallback synchronizer (
/sdk/latest-all) is always added, including whendataSystem.dataSourceiscustom.Updates contract-test wiring to match the current
feat/fdv2harness: CI now checks out the branch directly, the contract-test client config now accepts lists ofsynchronizers/initializersand buildscustomDataSourceOptionsaccordingly, and one FDv2 suppression is removed to re-enable the basic initializer test.Written by Cursor Bugbot for commit 6864953. This will update automatically on new commits. Configure here.