Keep the actual fieldnames around in BuilderInfo about protobuf.dart HOT 7 CLOSED

It's not quite what you want, but the field names and other data from the original DescriptorProtos are available via $json constants in 0.4.1.

See these two CL's:

dart-archive/dart-protoc-plugin@fc968d3

dart-archive/dart-protoc-plugin@f4a0f18

from protobuf.dart.

What happened to these constants? Can't see them in the generated files.

from protobuf.dart.

What happened to these constants? Can't see them in the generated files.
They are in the protoname.pbjson.dart file

from protobuf.dart.

@szakarias This will have to be fixed before we can implement proto3 json en-/decoding.

from protobuf.dart.

Looking into this it seems that the right thing is to use the FieldDescriptorProto.jsonName instead of our own mangled name.
That indeed is converted to camelcase, but with slightly different disambiguations from when we make dart names.
That makes our job simple.

from protobuf.dart.

Reading more we might need both names:
https://developers.google.com/protocol-buffers/docs/proto3#json_options

Proto3 JSON parsers are required to accept both the converted lowerCamelCase name and the proto field name.

Also textProto requires the proto field name.

That seems to be expensive in terms of size of the compiled program. Will have to consider this further...

from protobuf.dart.

This should be fixed now.

from protobuf.dart.