feat: add display name to golang protobuf

[pedroandrade]

Summary by CodeRabbit

• New Features
  • Added support for an optional display name field in services, allowing services to include a user-friendly name.

[coderabbitai]

Walkthrough

A new optional string field named display_name was added to the Service message in the device/device.proto protobuf schema, assigned field number 17. No other semantic changes were made, aside from minor whitespace cleanup on an unrelated field.

Changes

Cohort / File(s)	Change Summary
Protobuf Schema Update device/device.proto	Added optional display_name field to Service message; removed trailing whitespace from public_ips.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A string named display_name now hops in,
To Service it brings a new way to begin.
With fields all aligned and whitespace trimmed,
The proto’s more friendly, its future not dimmed.
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ME-4924-add-display-name-to-sockets

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

device/device.proto (1)

70-70: Field addition is wire-compatible; add comment to avoid confusion with existing name.

Tag 17 is unused, so adding display_name is fully backward-compatible.
Because the message now has both name and display_name, downstream consumers may be uncertain which to surface in UIs or logs. A brief inline comment such as // human-readable label for dashboards would remove ambiguity.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between adcd43d and 85286c9.

⛔ Files ignored due to path filters (3)

• device/device.pb.go is excluded by !**/*.pb.go
• gen/kotlin/border0/device/v1/ServiceKt.kt is excluded by !**/gen/**
• gen/swift/device.pb.swift is excluded by !**/gen/**

📒 Files selected for processing (1)

• device/device.proto (1 hunks)

🔇 Additional comments (1)

device/device.proto (1)

70-70: If presence tracking is required, declare the field as optional string.

The PR description calls this an “optional string”, but the field is declared as plain string.
In proto3 scalars are nullable but lack presence checks (has_display_name). If Go code needs that signal, mark it:

optional string display_name = 17;

(protoc ≥ 3.12) or wrap with google.protobuf.StringValue.