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
{{ message }}
This repository was archived by the owner on Jan 4, 2023. It is now read-only.
The two foo.protos declare different packages but for some reason if the service in services/foo/foo.proto imports common/foo.proto the service fails to load. If I simply rename common/foo.proto to something else everything is happy.
I noticed this line that looks suspicious. It seems loadProtos is taking the last token of the file path and using it as a lookup key? Could that be the source of the issue? If so, is there any reason why not to use the full path as the key?
I have a file structure like:
The two
foo.protos declare different packages but for some reason if the service inservices/foo/foo.protoimportscommon/foo.protothe service fails to load. If I simply renamecommon/foo.prototo something else everything is happy.I noticed this line that looks suspicious. It seems
loadProtosis taking the last token of the file path and using it as a lookup key? Could that be the source of the issue? If so, is there any reason why not to use the full path as the key?