Thank you for clarifying !!
On Tuesday, January 25, 2022 at 9:52:43 AM UTC-8 deanna...@google.com wrote:
> The leading dot is purposeful, and as pointed out is because the name is
> absolute rather than relative. Your workaround is fine, or you could use
> substring to get rid of the dot in the
The leading dot is purposeful, and as pointed out is because the name is
absolute rather than relative. Your workaround is fine, or you could use
substring to get rid of the dot in the type if you would like.
On Wednesday, December 22, 2021 at 11:22:38 AM UTC-8 vdu...@chegg.com wrote:
> Thank yo
Thank you Marc.
When I have leading dot, we are facing issues with schema confluent schema
registry integration.
1. We register schema without leading dot.
2. Confluent Schema registry uses the descriptor data to look up schema def
for a given protobuf message since descriptorData has extra do
IIRC, the leading dot means that the name is absolute rather than relative.
I'm not sure it represents an error.
On Wed, 22 Dec 2021, 19:00 'Venkat Duddu' via Protocol Buffers, <
protobuf@googlegroups.com> wrote:
> We are seeing extra dot for external referenced variables in
> descriptorData in t
We are seeing extra dot for external referenced variables in descriptorData
in the generated java class for a given Message.
*Message Definition*
syntax = "proto3";
package com.chegg;
import "google/protobuf/struct.proto";
message OneGraphRequest {
string operation_name = 1;
google.protobuf.Str
