Add PropertyNamingSource enum to support proto field names#70
Merged
Conversation
Co-authored-by: Havret <9103861+Havret@users.noreply.github.com>
Co-authored-by: Havret <9103861+Havret@users.noreply.github.com>
Co-authored-by: Havret <9103861+Havret@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add support for JSON property names from .proto files
Add PropertyNamingSource enum to support proto field names
Nov 9, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Extends JSON property naming control by introducing a
PropertyNamingSourceenum that replaces the booleanUseProtobufJsonNamesflag, adding support for using original .proto field names.Changes
New
PropertyNamingSourceenum with three options:Default- UsesPropertyNamingPolicy(existing default)ProtobufJsonName- Uses protobufJsonName(camelCase or customjson_name)ProtobufFieldName- Uses original .proto field name (e.g.,double_property)Backward compatibility:
UseProtobufJsonNamesmarked obsolete, maps to new enumUpdated
ProtobufConverter: RefactoredGetConvertNameFuncto use switch on enum, accessingdescriptor.Namefor field namesUsage
Works correctly with custom
json_namein .proto files -ProtobufFieldNameuses the original field name regardless ofjson_nameoverrides.Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.