Support for Proto3 well known types
See original GitHub issueFirst of all, thanks for this plugin, very useful.
Is your feature request related to a problem? Please describe. I am using proto3, and importing some well know types. It seems that these are not currently supported out of box, since I am getting a “File not found” error on the import, and an “Unresolved reference” error on all usages.
Describe the solution you’d like It would be great if protobuf/src/google/protobuf/ was automatically added as an include path of this plugin.
Additional context
Example:
syntax = "proto3";
import "google/protobuf/timestamp.proto";
package myproto;
message MyMessage {
google.protobuf.Timestamp created_at = 1;
}
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:11
Top Results From Across the Web
Google.Protobuf.WellKnownTypes Namespace
SourceContext represents information about the source of a protobuf element, like the file in which it is defined. Wrapper message for string ....
Read more >Don't Do It All Yourself: Exploiting gRPC Well Known Types in ...
Here's what I need to import two well known types, timestamp and empty in my .proto file: import "google/protobuf/timestamp.proto"; ...
Read more >What are well-known types? - Google Groups
The well-known types all have different purposes. The wrapper types allow for optional primitive fields, Any is a replacement for proto2 extensions, and...
Read more >Protobuf scalar data types - gRPC for WCF developers
Protobuf doesn't directly support the Guid type, known as UUID on other platforms. There's no well-known type for it. The best approach is...
Read more >Protocol Buffers v3 | Cloud APIs
It supports both binary and text wire formats, and works with many different wire protocols on different platforms. Proto3 is the latest version...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
A few other experiments.
Opening
/hello_go
with IntelliJThis does not seem to be a Goland specific issue per se, since repeating the same 3 steps with IntelliJ instead of Goland leads to the same result.
Opening
/hello_java
with IntelliJInterestingly, repeating the same 3 steps with IntelliJ and with the
hello_java
folder does not lead to any issue:However, inspecting the project structure or navigating to the declaration of
google.protobuf.timestamp
show that the plugin picks it up not from the bundled protobuf distribution, but from the"com.google.protobuf:protobuf-java:3.7.0"
gradle dependency required for the generated java code to compile.Opening
/
with GolangFinally, opening the root folder of the repo with Goland works fine:
And in that case, the bundled protobuf distribution appears in
/.idea/MRE_protobuf_plugin.iml
:Conclusion
So to me, the issue seems to stem from the fact that both IntelliJ and Goland only include the bundled protobuf distribution if there is a .proto file within the project.
I hope that helps, thanks for the time you are spending on this.
This issue is closed as plugin is not supported anymore. Please switch to https://github.com/jvolkman/intellij-protobuf-editor.