Skip to content

core(protocol): pnpm protocol:check for new deviceFamily field#27589

Merged
obviyus merged 1 commit into
openclaw:mainfrom
huntharo:chore-device-family-protocol-check
Feb 26, 2026
Merged

core(protocol): pnpm protocol:check for new deviceFamily field#27589
obviyus merged 1 commit into
openclaw:mainfrom
huntharo:chore-device-family-protocol-check

Conversation

@huntharo

@huntharo huntharo commented Feb 26, 2026

Copy link
Copy Markdown
Member

@huntharo huntharo changed the title core(protocol): pnpm protocol:check core(protocol): pnpm protocol:check for new deviceFamily field Feb 26, 2026
@greptile-apps

greptile-apps Bot commented Feb 26, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Adds the missing deviceFamily optional field to the DevicePairRequestedEvent Swift struct in both the macOS app and shared OpenClawKit protocol models, bringing them in sync with the existing TypeScript protocol schema (DevicePairRequestedEventSchema). This is a mechanical protocol sync — the field was already defined server-side and sent by clients, but the Swift decoder was missing it.

  • Added devicefamily: String? property, init parameter, assignment, and CodingKeys mapping ("deviceFamily") to DevicePairRequestedEvent in both apps/macos/ and apps/shared/ GatewayModels.swift
  • Both files remain identical after the change, as expected

Confidence Score: 5/5

  • This PR is safe to merge — it's a mechanical protocol sync adding a missing optional field to Swift models.
  • The change adds a single optional String? field to a Codable struct in two identical Swift files. The field already exists in the TypeScript protocol schema, is already sent by clients, and is already handled server-side. The CodingKeys mapping is correct, the placement is consistent with the schema field order, and both files remain in sync. No logic changes, no risk of runtime breakage.
  • No files require special attention.

Last reviewed commit: 8504095

@obviyus
obviyus merged commit 62a248e into openclaw:main Feb 26, 2026
26 checks passed
@obviyus obviyus self-assigned this Mar 23, 2026
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.

2 participants