Skip to content

docs: Add an OpenFeature feature matrix to the README - #30

Open
kinyoklion wants to merge 1 commit into
mainfrom
devin/1788211618-php-feature-matrix
Open

docs: Add an OpenFeature feature matrix to the README#30
kinyoklion wants to merge 1 commit into
mainfrom
devin/1788211618-php-feature-matrix

Conversation

@kinyoklion

@kinyoklion kinyoklion commented Aug 31, 2026

Copy link
Copy Markdown
Member

Adds a feature matrix to the README, mirroring the OpenFeature PHP SDK's own matrix, so a reader can see at a glance what this provider does and does not do.

  • Most unsupported rows are limitations of the OpenFeature PHP SDK, not of this provider — eventing, shutdown, named clients, tracking, transaction context and flag metadata have no place in that SDK's provider interface — and each row says so, so they are not read as provider gaps.
  • Format matches the matrices added to the Java, Python, .NET and JavaScript providers this week, so the providers can be compared side by side.
Implementation details

Rows and statuses were checked against the OpenFeature PHP SDK 2.3.0 and the LaunchDarkly PHP SDK 6.8.3 rather than copied from another provider: OpenFeature\interfaces\provider\Provider declares only the five resolve*Value methods plus hooks, logger and metadata accessors, ProviderAware holds a single provider for the whole API, and neither EvaluationDetails nor ResolutionDetails carries flag metadata.

The three separate fixes opened alongside this (#27, #28, #29) are provider-side bugs within rows the matrix marks as supported, so they do not change any status here.

Requirements

  • I have added test coverage for new or changed functionality
  • I have followed the repository's pull request submission guidelines
  • I have validated my changes against all supported platform versions

Related issues

None.

Describe the solution you've provided

A ## Feature matrix section after the supported-versions section, with the same Status | Feature | Notes shape as the other LaunchDarkly OpenFeature providers.

Describe alternatives you've considered

Listing only the rows the OpenFeature PHP SDK's own matrix has: it would drop initialization, tracking, transaction context and flag metadata, which are exactly the rows readers coming from another LaunchDarkly provider will look for.

Additional context

Testing: documentation only; make check still passes.

Link to Devin session: https://app.devin.ai/sessions/38a6eaf69fcf41109e136a1d0fe5e899
Open in Devin Desktop: https://app.devin.ai/desktop/session/38a6eaf69fcf41109e136a1d0fe5e899?variant=devin
Requested by: @kinyoklion


Note

Overview
Adds a Feature matrix section to the README (after supported PHP versions), aligned with the OpenFeature PHP SDK feature list and the same table shape used on other LaunchDarkly OpenFeature providers.

The table lists each capability with ✅/❌ status and notes: supported areas (flag types, targeting, hooks, logging, MultiProvider, extending via LDClient) and unsupported rows that call out whether the gap is the OpenFeature PHP SDK (e.g. named clients, eventing, shutdown, tracking, transaction context, flag metadata) versus provider behavior.

Reviewed by Cursor Bugbot for commit da8803a. Bugbot is set up for automated code reviews on this repo. Configure here.

Co-Authored-By: rlamb@launchdarkly.com <4955475+kinyoklion@users.noreply.github.com>
@devin-ai-integration

Copy link
Copy Markdown
Contributor

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

@devin-ai-integration

Copy link
Copy Markdown
Contributor

@cursor review

@kinyoklion
kinyoklion marked this pull request as ready for review August 31, 2026 21:29
@kinyoklion
kinyoklion requested a review from a team as a code owner August 31, 2026 21:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant