Comments (2)
@TeavenX, this is working as intended. The FindMessage
method of *desc.FileDescriptor
searches only the given file for the message. It does not search its imports.
You could recursively crawl through the files imports (and their imports possibly -- depending on if you want to search the entire transitive graph or not) and call FindMessage
on each one to find it.
Also, the protoparse package has been effectively replaced by protocompile. I'm working on a v2 of this repo and it will not included protoparse; users should instead migrate to the protocompile module.
In the protocompile module, what you're looking for does in fact exist: you can use linker.ResolverFromFile
on one of the linker.File
instances returned from compilation. That will find any symbol that is visible to the file. So, in your example, the symbol B.MsgInB
is visible to A.proto
because it imports B.proto
, so it would successfully find the symbol.
from protoreflect.
Thanks for reply, that helps a lot. For now, I define a dfs func to search transitive graph to find Message. And I will switch this package to protocompile next time, cause of the project ddl🤦
from protoreflect.
Related Issues (20)
- Any method for setting nested MessageKind field HOT 4
- Cannot add nested message and a field with same name using `builder` HOT 2
- panic: invalid type: got *dynamicpb.Message when GetExtension HOT 6
- Breaking changes in the protocompile/ast dependency
- EnumBuilder panics if it contains EnumValue with explicitly set Number HOT 1
- might not be bug: false duplication report due to use of relative path instead of absolute path HOT 6
- SIGSEGV: panic: runtime error: invalid memory address or nil pointer dereference in v1.15.2 HOT 8
- Protoreflect doesn't fall back to to v1alpha when a gRPC unimplemented response is returned HOT 1
- String escaping in protoprint is wrong HOT 1
- First enum value must be 0 in proto3 [protoprint] HOT 2
- missing `{}` after printing option HOT 5
- Upgrade protocompile to v0.7.0 HOT 3
- go build error HOT 3
- Regression upgrading from v1.14.1 to v1.15.4: extensions are resolved recursively instead of non-recursively HOT 1
- Regression upgrading from v1.14.1 to v1.15.4: absolute paths no longer accepted by parser.ParseFilesButDoNotLink HOT 3
- Regression upgrading from v1.14.1 to v1.15.4: new mustBeSource constraint/check HOT 5
- Stub structure and Methods will relay on protobuf API V2 HOT 13
- Fail to compile proto file HOT 2
- Tests broken with google.golang.org/protobuf v1.33.0
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from protoreflect.