Repository navigation
docs: Fix invalid Python in the README context examples - #75
Merged
Merged
Conversation
Co-Authored-By: Ryan Lamb <4955475+kinyoklion@users.noreply.github.com>
Contributor
|
I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".
|
keelerm84
approved these changes
Nov 6, 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.
Requirements
Related issues
None. Found during the weekly OpenFeature provider audit.
Describe the solution you've provided
The
EvaluationContextexamples in "OpenFeature Specific Considerations" did not run as Python: they usednull/true,,in place of:in dict entries, a[ ... "anonymous" = > true ]list for the user context, and a trailing;. The "private attributes in a multi-context" example also set"kind": "organization"rather than"multi", so it described a single context with nested attributes instead of the multi-context the heading names.Each example now executes, and each one converts through
EvaluationContextConverterto a valid LaunchDarkly context of the intended shape (checked againstopenfeature-sdk0.10.0 andlaunchdarkly-server-sdk9.20.0).Describe alternatives you've considered
None.
Additional context
Docs only; no code changes.
Link to Devin session: https://app.devin.ai/sessions/f7bc946afe8c41a28cf7f3f497fc8b9d
Open in Devin Desktop: https://app.devin.ai/desktop/session/f7bc946afe8c41a28cf7f3f497fc8b9d?variant=devin
SDK-3496
Note
Overview
README-only fix for the OpenFeature
EvaluationContextexamples under “OpenFeature Specific Considerations.”The snippets now use valid Python: dict entries use
:instead of,,None/Truereplacenull/true, trailing semicolons are removed, and nesteduser/organizationblocks are dicts rather than malformed lists or"anonymous" = > truesyntax. The private attributes in a multi-context example now sets"kind": "multi"(was"organization") so it matches the section title and the intended multi-context shape.Reviewed by Cursor Bugbot for commit d6e47f3. Bugbot is set up for automated code reviews on this repo. Configure here.