[kinyoklion]

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 (local run on PHP 8.5; CI covers 8.2–8.4)

Related issues

Found during the OpenFeature provider audit against the LaunchDarkly OpenFeature provider spec (OFP context conversion: date/time values must be converted to an ISO-8601 representation in UTC).

Describe the solution you've provided

EvaluationContextConverter passed custom attribute values to LDContextBuilder::set unchanged. OpenFeature PHP evaluation contexts can carry DateTime/DateTimeImmutable values, which the LaunchDarkly context model cannot represent, so date attributes could not be used with the before/after operators.

Custom attribute values are now converted recursively (top level, nested arrays, and individual contexts inside a multi-context):

• DateTimeInterface values become UTC ISO-8601 strings with millisecond precision (e.g. 2024-03-01T00:30:00.123Z), a format the PHP SDK's date operators parse.
• Scalars, null, and arrays keep their current behavior.
• Any other value (for example, an arbitrary object nested in an array) becomes null and an error is logged.

Describe alternatives you've considered

Formatting as Unix milliseconds. The LaunchDarkly date operators accept both, but the spec calls for ISO-8601 strings, which also keeps the value readable in the LaunchDarkly UI.

Additional context

make check passes locally (cs-check, phpstan, phpunit).

Link to Devin session: https://app.devin.ai/sessions/b809f0f4a45a48c9a1c079faebb5c70a
Open in Devin Desktop: https://app.devin.ai/desktop/session/b809f0f4a45a48c9a1c079faebb5c70a?variant=devin

---

Note

Overview
OpenFeature evaluation contexts can include DateTime / DateTimeImmutable on custom attributes, but those values were passed straight into LDContextBuilder::set, so they did not work with LaunchDarkly before / after date targeting rules.

EvaluationContextConverter now normalizes every custom attribute (including nested arrays and multi-kind sub-contexts) through a new toLdValue helper before calling set. DateTimeInterface values are converted to UTC ISO-8601 strings with millisecond precision (e.g. 2024-03-01T00:30:00.123Z). Scalars and null are unchanged. Values that cannot be represented (such as arbitrary objects inside arrays) become null and trigger a logged error.

Tests cover top-level and nested dates, multi-context dates, and the unconvertible-value path.

^{Reviewed by Cursor Bugbot for commit fda8ff5. Bugbot is set up for automated code reviews on this repo. Configure here.}

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring