You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both proto/google/fhir/proto/r4/core/datatypes.proto and proto/google/fhir/proto/r4/core/profiles/datatypes.proto generate a class named DatatypesReflection as part of the standard output from protoc. Both *.proto files use the same package google.fhir.r4.core. This results in a duplicate name collision in the generated output.
This problem disappears if the datatypes.proto file is moved into the google.fhir.r4.core.profiles namespace.
Tho' I am not certain if that causes any other unrelated issues.
The text was updated successfully, but these errors were encountered:
Got it ... I'll take a look at the Bazel configuration. It may be a while as I'm working on other elements of the project. If I come up with something, I'll contribute back.
Both
proto/google/fhir/proto/r4/core/datatypes.proto
andproto/google/fhir/proto/r4/core/profiles/datatypes.proto
generate a class namedDatatypesReflection
as part of the standard output fromprotoc
. Both*.proto
files use the same packagegoogle.fhir.r4.core
. This results in a duplicate name collision in the generated output.This problem disappears if the
datatypes.proto
file is moved into thegoogle.fhir.r4.core.profiles
namespace.Tho' I am not certain if that causes any other unrelated issues.
The text was updated successfully, but these errors were encountered: