refactoring config parser tests
adding scope to config
possible values: 'file' or 'project'
if nothing is specified or an invalid value is specified we default to project scope.
no need to have separate config parsers
update action factory to take a list of file paths and return multiple actions
generate one action pre file
movin file change consumer tests to own test suite
filter the files sent to action factory based on command scope
queue all file actions, not just the first
restructuring actions
enabled per file actions
need to test properly later since my local setup is in a non working state at the moment
some cleanup in command flow
don't produce error messages when unable to parse log
override ToString for ShellCommand so the logging will make some kind of sense
file change consumer is broken, starting with test refactoring since the tests where beginning to get unreadable and unmaintainable. non working state right now, will look in to this later.
fixed trigger vs. files changed vs. action generation
update command substitutions
now possible to specify:
{absolute-file-path}
{relative-file-path}
{project-root}
{working-directory}
added a config builder
added command substitutions for solution root path
trying out ErrorListProvider for error messages
playing around with different command runners