Repository navigation
chore: Remove the leftover experimental note from the data system config - #540
Merged
Merged
Conversation
jsonbailey
marked this pull request as ready for review
October 19, 2026 15:27
kinyoklion
approved these changes
Oct 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
The GA cleanup in #428 removed the FDv2 pre-release warnings, but it missed the docs for
datasystem_configinConfigandAsyncConfig. Those still say the option is experimental and needs direction from LaunchDarkly support. This removes the sentence from the parameter and property docs.Note
Overview
Updates public API docs for
datasystem_configonConfigandAsyncConfigso they match the GA data-system work from #428.The constructor
:param datasystem_config:text no longer calls the option experimental or says to contact LaunchDarkly support. It now states that the data system controls how the SDK loads flag and segment data, and that setting it overridesfeature_store,update_processor_class,stream, anduse_ldd.The
datasystem_configproperty docstrings are aligned the same way (purpose only, no experimental warning). No runtime or config behavior changes—docstrings only.Reviewed by Cursor Bugbot for commit bb1012b. Bugbot is set up for automated code reviews on this repo. Configure here.