v0.6.1

• Minor adjustments to README

v0.6.0

Added

• Allow specifying Checks With Tag(s), so only checks with specified tags are used by credo (#30)
• Allow specifying Checks Without Tag(s), so checks with specified tags are ignored by credo (#30)

Changed

• Changed display name to Credo (Elixir Linter)

v0.5.0

Changed

• rework internal ConfigurationProvider: instead of using a singleton, use functional approach

Fixed

• Fixes evaluation of triggers within Credo issues as they can be arrays or other unknown types (#27)

v0.4.5

Fixed

• Only add the configuration file configured in the extension's configuration to all found configuration file
  if it's an absolute path, the file exists, and it is not already found (#4)
• File paths in the output channel are not surronded by quotes anymore to resolve issues when opening these paths with Cmd + Click / Ctrl + Click

v0.4.4

Fixed

• Only interrupt if an exit status code like ENOENT, 126 or 127 is present instead of using the stderr as well

v0.4.3

Fixed

• Only interrupt due to errors when credo's exit status is ENOENT, 126, or 127, or when credo logs something to stderr

v0.4.2

Changed

• Improve error reporting
  • Show proper error codes when executing commands and more information
  • Show working directory of a process executing credo
  • Fix a typo in an error message

v0.4.1

Fixed

• Fixed Windows Support (#18, #19)

v0.4.0

Added

• Support multiple workspaces (#8)
• Add an output channel to track the extension's processes
  • Added a configuration option enableDebug that enables extensive logging to the output channel, such as
    • configuration changes
    • spawned processes
    • credo CLI args
    • etc.

Changed

• Remove configuration option onSave as this is the default and probably not toggled by anyone
• Rework of the codebase (no further changes in functionality)
• Increase test coverage

v0.3.0

Added

• Support this extension also on Windows platforms by using the mix executable mix.bat (#10)
• Respect Credo's settings for including/excluding files when linting an Elixir file. (#6)
  • Added a config named lintEverything that enables one to bypass the config's file inclusion/exclusion mechanism if set to true,
    and, thus, lint any Elixir file.
• Only mark the trigger in the line, even if credo adds method arity to the trigger

Changed

• Forward any warning/error message coming from credo itself (#8.1)

Fixed

• Fixed a bug where no credo command was issued after a command was cancelled (when a document was closed/deleted, for instance)
• Fixed bug where credo issues with the field trigger present, but without the trigger occurring unchanged in the line of the issue would not be created. (#9)