-
Notifications
You must be signed in to change notification settings - Fork 0
Add display name to common service #58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Verification agent
❓ Verification inconclusive
optionalkeyword missing – current field has no presence trackingThe PR description and AI summary both state that
display_nameshould be an optional field.In proto3, presence tracking for singular scalars (so that you can tell unset vs empty string) is only available when the field is declared with the
optionalkeyword:Declaring it without
optional(as in the current diff) turns it into a regular scalar with no presence information; clients cannot distinguish""from not provided, which is often undesirable for UI-facing “display name” semantics.Confirm that all language targets used in your tool-chain are on protobuf ≥ 3.15 (released 2020-12) where
optionalis supported; otherwise code-gen will fail.Add
optionaltodisplay_namefor presence trackingThe
display_namefield incommon/messages.protoneeds theoptionalkeyword so that clients can distinguish “unset” from an empty string. Without it, proto3 treats the field as a regular scalar with no presence information.File:
common/messages.proto(around line 114)Suggested change:
• After updating, ensure your proto compiler and all language generators are using protobuf >= 3.15 (optional fields were introduced in v3.15.0) to avoid code-gen failures.
🤖 Prompt for AI Agents