Fix assertion config error - Gonzales-3.2 #588
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #563
This is one I've sort of known about for a long time but finally got round to investigating it a bit.
Currently if you're using the CLI and you don't supply a path a config file or have a config file in the root of your project then the config loader throws an error to say it can't find a path. This was mainly down to the way the config loader would fall back to your package.json if it couldn't find a
.sass-lint.yml
file, the logic wasn't taking into account a scenario where that path wasn't specified in your package file.This resolves it and adds a test to ensure this error doesn't reoccur.
I've pointed it towards the gonzales 3.2 update branch as I don't want to have to keep updating that one with new develop work, we may as well just load it all together in preparation for 1.6.
<DCO 1.1 Signed-off-by: Dan Purdy danjpurdy@gmail.com>