v0.8.0

• Fixes an issue where the protolint.lint setting was not visible in the Settings section within VSCode.

npm audit

• Bump minimist from 1.2.5 to 1.2.6 by @dependabot in #28

Full Changelog: v0.7.0...v0.8.0

v0.7.0

CHANGES

• Add the protolint.path setting to allow for setting where the protolint binary lives.
• No longer show an error dialog when a protolint config file cannot be found.
• Respect nested protolint configuration files (use the protolint config closest to the proto file).

v0.6.0

ENHANCEMENTS

• Better error handling for errors that propagate from the protolint binary. These will now be shown as an error window within VSCode.
• Run the linter when a file is opened, in addition to when a file is saved.
• Add protolint.lint as a command within VS Code.

v0.5.1

BUG FIXES

• Resolve an issue that caused proto files that had a space in their path to not be linted. ( Thanks @Strandinator 🎉 )

v0.5.0

ENHANCEMENTS

• Add support for multiple workspaces. ( Thanks @silenceisgolden 🎉 )

v0.4.0

BUG FIX

• Fix an issue where listing results would not be returned on Windows architectures

v0.3.0

• Use the current workspace directory as the configuration directory when calling protolint

v0.2.0

Add proto to the list of activation events

v0.1.0

Initial release of vscode-protolint