chore: Fix segment key in FileData example (includes → included)

[dyozie-ld]

What

Fixes a functional error in the FileData docstring example. The segments object uses "includes" for the list of context keys:

"segments": {
  "segment-key-1": {
    "key": "segment-key-1",
    "includes": [ "user-key-1" ]
  }
}

Why

The segment model (LaunchDarkly::Impl::Model::Segment) deserializes included / excluded, never includes:

@included = data[:included] || []
@excluded = data[:excluded] || []

An unknown "includes" key is silently dropped and included defaults to an empty array, so a context listed under includes is never actually added to the segment. The example doesn't work as written.

Change

"includes" → "included" in the FileData docstring (lib/ldclient-rb/integrations/file_data.rb). Docstring-only; no code behavior change.

Note

The same example is shared across LaunchDarkly's SDK docs; a companion fix to the canonical snippet source is in launchdarkly/sdk-meta#541.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only change in a comment example; no production code paths are modified.

Overview
Corrects the FileData integration docstring JSON example so segment membership uses "included" instead of "includes".

That matches how LaunchDarkly::Impl::Model::Segment reads segment data (data[:included]); copying the old example would leave included empty and segment targeting would not work as documented. Docstring-only—no runtime behavior change.

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

[jsonbailey]

Thanks @dyozie-ld