You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Passing any options, including empty object to sass doc i.e. sassdoc({}) will not load .sassdocrc. Reason being that if the option is object, it will not load default config, but instead assume it has been loaded.
If it's wanted behaviour, then consider this not a bug report, but rather a feature request. To me, it makes perfect sense to be able to pass both configuration file and options.
I would imagine that the scenario I stumbled upon, having multiple directories with sass files that need to be documented with some common and specific settings, isn't unique. Those are the cases where the common settings could be passed as object and the speccific setings as config file.
I understand, if you're willing to rephrase the issue under a "feature request", and detail the needs and expectations, it can maybe be considered for the next major (whenever that be...). Changing that sort of behaviour on the current major would probably bring too much troubles.
Passing any options, including empty object to sass doc i.e.
sassdoc({})
will not load.sassdocrc
. Reason being that if the option is object, it will not load default config, but instead assume it has been loaded.sassdoc/src/environment.js
Lines 73 to 90 in 21bf591
Tested with 2.7.1.
The text was updated successfully, but these errors were encountered: