Closed jhlee0133 closed 1 month ago
Hi! Thanks for opening your first issue here! :smile:
Yes, currently frb does not distinguish same struct name in different files. This is because there can be complex nested use
etc with edge cases. The simplest solution is to rename your structs to avoid name conflicts, or try to configure the protobuf codegen to add prefix.
Ok, thank you for your response.
You are welcome!
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new issue.
Describe the bug
when using two protobuf files (a.proto and b.proto) that define response messages with the same name but different structures and generating _
frb_generated.rs
_ file, the file produces a type mismatch errora.proto:
b.proto:
api:
frb_generated.rs error:
Steps to reproduce
https://github.com/jhlee0133/frb_example
Logs
Expected behavior
No response
Generated binding code
No response
OS
macOS 15.0.1
Version of
flutter_rust_bridge_codegen
2.5.0
Flutter info
No response
Version of
clang++
No response
Additional context
No response