.protolint.yaml can't affect vscode-protolint

[IS-Martin]

As the title and my version info are as follows

• vscode version: 1.43.0
• vscode-protolint version: 0.2.0
• protolint version: v0.23.2
• go version: go1.14 (and using gvm)

My proto

My .protolint.yaml

My file structure

- root
  - definition
    - myproto.proto
  - .protolint.yaml

and also tried

- root
  - definition
    - myproto.proto
    - .protolint.yaml

Just wondering why the .protolint.yaml didn't affect vscode linting as expected.

[jpreese]

Thanks for submitting the issue @MartinChangCF! We'll definitely take a look at this.

In the meantime, have you tested your configuration with just protolint on the command line? I'd like to rule out a protolint specific issue.

[IS-Martin]

Sorry for the late reply @jpreese

I tried the protolint command

protolint  ./

and with --config_dir_path

protolint  --config_dir_path=./ ./protoc

they both work properly.

[jpreese]

Thanks. I did some investigation on this end as well and am definitely seeing some odd behavior. It does work if the .protolint.yaml file is in the same directory as the proto definitions.

I'll do some more digging and see what we can do to get this resolved.

[jpreese]

@MartinChangCF this should now be resolved in v0.3.0 -- could you confirm at your earliest convenience? Thanks again for reaching out 👍

[IS-Martin]

@jpreese Thanks for your updates! It works now 👍

[jpreese]

Awesome, glad to hear.