Skip to content

docs(adapters): fix mapping hostname field name in usage page#288

Merged
pllesperance-lc merged 1 commit into
masterfrom
docs/fix-adapter-mapping-hostname-field
Jul 2, 2026
Merged

docs(adapters): fix mapping hostname field name in usage page#288
pllesperance-lc merged 1 commit into
masterfrom
docs/fix-adapter-mapping-hostname-field

Conversation

@pllesperance-lc

Copy link
Copy Markdown
Contributor

Summary

  • The "Configurations" list on the adapter usage page documented client_options.mapping.hostname, which does not exist in the adapter code.
  • Corrected to client_options.mapping.sensor_hostname_path, the actual field name.

Verification

  • Confirmed against the adapter source: MappingDescriptor.SensorHostnamePath carries the tag sensor_hostname_path in go-uspclient (protocol/mapping.go), and there is no hostname key under mapping.
  • The "extractors" list later on the same page already used the correct name; the two listings are now consistent.
  • Grepped the docs tree — this was the only occurrence of the incorrect form. Note that client_options.hostname (top-level, the adapter's own hostname) is a real field and was left untouched.

🤖 Generated with Claude Code

The Configurations list referenced client_options.mapping.hostname,
which does not exist. The actual field is
client_options.mapping.sensor_hostname_path, matching the
SensorHostnamePath extractor (go-uspclient protocol/mapping.go) and
the extractors list further down the same page.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@pllesperance-lc pllesperance-lc merged commit ca09e60 into master Jul 2, 2026
2 checks passed
@pllesperance-lc pllesperance-lc deleted the docs/fix-adapter-mapping-hostname-field branch July 2, 2026 19:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant