Imports are not working

Here’s how to reproduce:

create a file date.proto

syntax = "proto3";

message Date {
  // Year of date. Must be from 1 to 9999, or 0 if specifying a date without
  // a year.
  int32 year = 1;

  // Month of year. Must be from 1 to 12.
  int32 month = 2;

  // Day of month. Must be from 1 to 31 and valid for the year and month, or 0
  // if specifying a year/month where the day is not significant.
  int32 day = 3;
}

create a file foo.proto

syntax = "proto3";

import "date.proto";

message Foo {
    Date date = 1;
}

You’ll get an error saying Date is undefined. Compiling with protoc itself works though…

I’m creating a course on Protobuf and I’m recommending your plugin, but that error is a roadblock to properly recording the video. Any chance you know how to solve this?

[justfalter]

Doing some debugging on vscode 1.31.1 on OSX with vscode-proto3 0.2.2 (code --inspect-extensions 12345, and then attaching using chrome debug tools), I can see that when vscode-proto3 gets to here: https://github.com/zxh0/vscode-proto3/blob/7fa48c3f4093b8537705207d99d42f1302620b10/src/proto3Compiler.ts#L71 , all of the paths have been expanded to absolute paths. For example, with:

"protoc": {
    "options": ["--proto_path=lib/proto", "--cpp_out=gen"]
}

The value of args being passed to execFile is

[
    "--proto_path=/abs/path/to/lib/proto",
    "--cpp_out=/abs/path/to/gen",
    "rel/path/to/my.proto"
]

This is expected to be the following for protoc 3.6.1 to work:

[
    "--proto_path=proto",
    "--cpp_out=gen",
    "rel/path/to/my.proto"
]

[nevir]

Running into similar issues. Is there a way of observing what protoc is being called with, and its output?