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
Hi there, very first time for me posting an issue here so sorry in advance if this is not the right place.
So here's the thing, I'm using vscode 1.59.1 with Java language support v0.81.0 and I ran into something weird when using protobuf.
Let say there’s a proto definition file in my service generating a class named and namespaced exactly the same as one that is in a library that is part of my service deps.
package bruce.proto.v1;
message Foo {
string bar = 1;
}
When writing var foo = Foo.newBuilder().setBaz(“qux”).build(); my service compiles successfully but vscode (as well as eclipse) complains that setBaz(String) is undefined for the type Foo.Builder.
When I cmd+click on Foo class it brings me to the generated class of the library instead of the one generated locally.
The classpath is set correctly and if I remove the library dependency the IDE doesn't complain anymore and Go To Definition works as expected.
Hi there, very first time for me posting an issue here so sorry in advance if this is not the right place.
So here's the thing, I'm using vscode 1.59.1 with Java language support v0.81.0 and I ran into something weird when using protobuf.
Let say there’s a proto definition file in my service generating a class named and namespaced exactly the same as one that is in a library that is part of my service deps.
Local definition file:
Imported library definition file:
When writing
var foo = Foo.newBuilder().setBaz(“qux”).build();
my service compiles successfully but vscode (as well as eclipse) complains thatsetBaz(String) is undefined for the type Foo.Builder
.When I cmd+click on
Foo
class it brings me to the generated class of the library instead of the one generated locally.The classpath is set correctly and if I remove the library dependency the IDE doesn't complain anymore and Go To Definition works as expected.
If you want to see by yourself
Then open test-java-app Java project in vscode or eclipse.
Cheers!
The text was updated successfully, but these errors were encountered: