Support for .jsbeautifyrc?
framerate opened this issue · comments
If this is supported, I think the documentation is missing. Thanks!
If you are taking about using .jsbeautifyrc if available without specifying in task, then I need to think about it. For now it needs to be specified in task.
I would prefer it as a fallback, but the task config should work. I want aware that we just called it "config" as I'm new to jsbeautify. I'll play with that setting tomorrow :)
Thanks!
—
Sent from Mailbox for iPad
On Fri, Jan 3, 2014 at 11:54 PM, Vishal Kadam notifications@github.com
wrote:
If you are taking about using .jsbeautifyrc if available without specifying in task, then I need to think about it. For now it needs to be specified in task.
Reply to this email directly or view it on GitHub:
#28 (comment)
I am planning to support "jsbeautifyrc" similar to https://github.com/gruntjs/grunt-contrib-jshint#jshintrc, I will keep "config" options for backward compatibility. Following will be supported values for jsbeautifyrc/config option.
{
false: Config will not be loaded from any file (Default value)
"path/to/file": Read all config from specified file. (Currently supported by "config" option)
true: Read .jsbeautifyrc from same folder for each file currently being beautified.
}
This is great. I think grunt-contrib-jshint does it perfectly! Great news!
Should this be closed?
Not yet, I haven't yet published this one. There are some scenarios I need to cover.
Oh, my bad! I saw that in master and thought it was released. Is master stable enough for "production" then?
From what I can see in the code, the feature is in the README but not implemented, am I right?
yeap.. Yet to implement it.
Alright thanks!
What is the status of this issue?
I have just completed the development of it. I too a slight different approach than discussed prior. Simple rule is if ".jsbeautifierrc" file exists use it instead of setting config value to true. See this commit.
Release 0.2.8 published