Follow imports

[baconalot]

Now I get errors from imported fields:

From: import "currency.proto";

It would be awesome if those import types are also imported.

[zxh0]

Hi, could you provide some more information? What is the error message?

[baconalot]

The message reads "currency.Currency" is not defined. Reproduction is easy:

"foo.proto"

syntax = "proto3";

package foo;

message Foo {
    string a = 1;
}

and in the same folder "bar.proto"

syntax = "proto3";

package bar;

import "foo.proto";

message Bar {
    foo.Foo a = 1;
}

yields the error message "foo.Foo" is not defined with the error marker on foo.Foo a = 1;

[zxh0]

Hi, maybe the problem is comes from import statement. How about change it to import "foo.proto";?

[baconalot]

Ow, my bad, that syntax is what I already use in real files. This still does not fix the issue, I still get the undefined error.

[zxh0]

This extension just calls protoc when it need to check proto syntax. So I guess the import path is not correct. How about import "path/to/foo.proto";?

[Iulian7]

I have the same problem. Both files are in the same folder. They compile fine using protoc on the command line.

[Tommy-42]

Hi,

I have the same issue described here.

Multiple proto files in the same directory ( same package so I dont prefix with xx.yyy but I import them ) and I also have "xxxx" is not defined

Protoc is able to compile those files too.

[zxh0]

hi @Tommy-42 could you provide a minimal folder with some proto files to let me reproduce this issue ? thank you

[Tommy-42]

Hey @zxh0 sure :)

This should trigger the error on vscode but compile fine with : protoc --go_out=. *.proto

test.zip

[hanyu363]

I have the same problem. "msg.base.ReqReconnect" is not defined.

The message is not normally identified

[zxh0]

@Tommy-42 it's weird that I am not able to reproduce the error (on both Windows and macOS) using test.zip you uploaded

[zxh0]

hi @hanyu363 could you give me a zip like Tommy-42 to let me reproduce the error?

[hanyu363]

proto.zip Is it related to setting up

[zxh0]

@hanyu363 我没办法重现你的问题，我给你邮箱发了一封邮件，请查收一下。

[hanyu363]

英文差，这么快就被识别出来了。 问题解决了。。应该需要设置一下Proto文件路径才可以。。 "protoc": { "path": "/usr/local/bin/protoc", "options": [ "--proto_path=/Users/weihua/workspace/CityGuardians/common/proto", ] } 谢谢啦。

[hanyu363]

If you open the proto directory alone, no problem. If proto is not the root directory, it needs to be explicitly specified in the vs configuration. Then restart the editor just fine. Please refer to "protoc": { "path": "/usr/local/bin/protoc", "options": [ "--proto_path=${workspaceRoot}/common/proto", ] }

[zxh0]

thank you @hanyu363

[mingweiLIU]

I have the same issue: the defined type that from imported proto file is marked as not defined by vscode-proto3. Both of the proto files are from the same folder named proto, I've tried to set proto_path=${workspaceRoot}/proto in setting.json, while it seems not work.

[zxh0]

@mingweiLIU please remove ${workspaceRoot} and use relative path in your settings.json

[mingweiLIU]

Thanks, it works now!

[luanxuechao]

@mingweiLIU I have the same issue,how to fix ?

[mingweiLIU]

@luanxuechao Just set proto_path=proto in setting.json will be ok (proto is the folder name of your proto files).

[awper361]

Encoutered the same issue, just restarted vscode then problem solved.

[zoe0316]

Encoutered the same issue, just restarted vscode then problem solved.

So do I.

[jpreese]

+1 same issue -- had to restart

[AliAlhajji]

I had the same problem (I use Windows 10) and I solved it by adding the following to my workspace settings.json:

{
    "protoc": {
        "path": "C:/Path/To/Protoc binary",
        "options": [
        "--proto_path=C:/path/to/my/protofiles/directory",
        ]
        }
}

[Sieboldianus]

I just found out:

the syntax

import "uphierarchy/message.proto";

works in VS code if uphierarchy is the folder from where vs code was started.

That means: No need to override settings.json locally

[CMCDragonkai]

If I have a multi-root workspace, how should this setting be written. Different roots will have different include paths?

[clayne11]

This isn't working for me. If I set the proto_path option VSCode is still unable to jump to definitions. If I open the Proto path in VSCode directly as the root, then it works.

[geovex]

For me it really doesn't work. After modifying settings.json errors aren't shown, and autocomplete will not suggest imported symbols (but sometime i can jump to definitions).