docs: Add an OpenFeature feature matrix to the README - #33
Open
kinyoklion wants to merge 1 commit into
Open
Conversation
Co-Authored-By: rlamb@launchdarkly.com <4955475+kinyoklion@users.noreply.github.com>
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
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.
Adds a feature matrix to the README mirroring the OpenFeature Ruby SDK's own feature table, so a reader can see at a glance what the provider does and does not support.
⚠️/❌so unsupported rows can state whether the limitation is in the OpenFeature Ruby SDK or is a provider gap.Implementation details
Requirements
Related issues
Follow-up to the audit of LaunchDarkly's OpenFeature providers, which produced #27, #28, #29, #30 and #31 in this repository.
Describe the solution you've provided
The matrix reuses the row set and legend of the OpenFeature Ruby SDK feature table so the two can be read side by side, and so the same format can be applied to the other LaunchDarkly providers. Statements about eventing, initialization, shutdown, tracking, and flag metadata were checked against the current implementation in
lib/ldclient-openfeature.Describe alternatives you've considered
Writing a LaunchDarkly-specific row set instead of mirroring OpenFeature's — rejected, since the point of the matrix is comparability with the OpenFeature SDK table and with the other providers.
Testing
Documentation only; no code changes.
Additional context
Screenshots and a staging preview do not apply to a README change in a server-side library.
Link to Devin session: https://app.devin.ai/sessions/0c452d209ec54b068ba120b4c92b8f6c
Requested by: @kinyoklion
Note
Overview
Adds an OpenFeature feature matrix to the README so readers can see at a glance what this provider supports.
The table mirrors the OpenFeature Ruby SDK feature list (providers, targeting, hooks, logging, domains, eventing, initialization, shutdown, tracking, transaction context, extending, flag metadata). Every row is marked supported, with notes on how the provider implements it or that the SDK handles it. The legend leaves room for partial/unsupported rows later.
Reviewed by Cursor Bugbot for commit 898abf3. Bugbot is set up for automated code reviews on this repo. Configure here.