Issue with package and --config #284
Description
Steps to reproduce:
pass a config file not at the root of the project.
$ bin/sassdoc src dest -vf -c somedir/conf.json
Case 1
"package": "package.json" which is wrong, should be relative to conf file. But anyway:
BTW: this should be clarified in the docs
[2014-12-01 18:29:52] [ERROR] Package file "undefined" not found.
[2014-12-01 18:29:52] [WARNING] Falling back to "package.json".
[2014-12-01 18:29:52] [WARNING] No package information.
[2014-12-01 18:29:52] [WARNING] No package information.
[2014-12-01 18:29:52] Folder "out" successfully refreshed.
[2014-12-01 18:29:52] [WARNING] No package information.
[2014-12-01 18:29:52] Folder "dev" successfully parsed.
[2014-12-01 18:29:52] theme "default" successfully rendered.
[2014-12-01 18:29:52] Process over. Everything okay!
"undefined" + 3 times No package information.
Case 2
no package key set in conf.json:
[2014-12-01 18:45:16] [WARNING] No package information.
[2014-12-01 18:45:16] [WARNING] No package information.
[2014-12-01 18:45:16] Folder "out" successfully refreshed.
[2014-12-01 18:45:16] [WARNING] No package information.
[2014-12-01 18:45:16] Folder "dev" successfully parsed.
[2014-12-01 18:45:17] theme "default" successfully rendered.
[2014-12-01 18:45:17] Process over. Everything okay!
3 times No package information.
If no package key is provided I guess we should still fallback to project root package.json ?
Impacting the plugins as well.