If there are messages nested in the proto file, the numbers will be recognised as strings about protoreflect HOT 2 CLOSED

I think I have found the root cause:

according to https://github.com/jhump/protoreflect/blob/main/dynamic/json.go#L386,
if dataType=int64, it will become strings due to strconv.FormatInt(), So I have a question, why we don't use https://github.com/jhump/protoreflect/blob/main/dynamic/json.go#L399 for dataType=int64

btw, I found the similar issue for uint64, https://github.com/jhump/protoreflect/blob/main/dynamic/json.go#L403

from protoreflect.

@Big-big-orange, this is part of the spec for the JSON format of protobuf messages: https://protobuf.dev/programming-guides/proto3/#json

64-bit integers are represented using JSON strings because JSON numbers are usually stored as IEEE 64-bit floats, which cannot represent all 64-bit integers. This is related to protocolbuffers/protobuf#12994.

Also, FWIW, I recommend users migrate their usage of "github.com/jhump/protoreflect/dynamic" to instead use "google.golang.org/protobuf/types/dynamicpb". A (hopefully soon) v2 of this repo will remove the dynamic package (and others) since this functionality is now provided by the core Protobuf runtime for Go.

from protoreflect.