Skip to content

Releases: pantajoe/vscode-elixir-credo

v0.2.0

12 Jan 10:45
Compare
Choose a tag to compare

Added

  • Added a configuration option ignoreWarningMessages in order to be able to ignore the following warning messages (especially if they come repeatedly, see #4):
    • "Found multiple files ... will use ..."
    • "... file does not exist. Ignoring ..."

Fixed

  • Improve warning message if the credo output is empty
  • Try to capture only the JSON-part of the credo output if it includes info messages from mix, for instance.

v0.1.1

24 Nov 08:33
Compare
Choose a tag to compare

Fixed

  • If the issue was found with the issue's trigger, include its last character.

v0.1.0

24 Nov 08:12
Compare
Choose a tag to compare

Added

  • Use credo issues' triggers to mark the correct substring (#2)

Changed

  • Display 'refactor' issues as Information instead of hints (#3).
    This allows the issues to be displayed more clearly and also shown in the Problems panel.

v0.0.5

27 Oct 08:02
Compare
Choose a tag to compare

Changed

  • Improved the warning message when the mix command does not work.

v0.0.4

26 Oct 17:14
Compare
Choose a tag to compare

Added

  • Added keywords elixir, credo, linter to the extension's package.json to make easier to find

v0.0.3

25 Oct 19:46
Compare
Choose a tag to compare

Added

  • Include the execute path given in the extension's config into the env variable PATH of the mix credo command
    • Solves issues for the asdf-vm when specifying an execute Path (asdf shims directory)

v0.0.2

25 Oct 16:25
Compare
Choose a tag to compare

Changed display name to 'Elixir Linter (Credo)'.

v0.0.1

25 Oct 16:12
Compare
Choose a tag to compare

Initial Release

This is the first release (v0.0.1) of the VSCode extension: Elixir Linter (supported by Credo).