Format/Schema of .jsbeatifyrc

[mokkabonna]

This tool only supports .jsbeautifyrc files with the js options on the first level of the JSON file.

That was fine until this project got formatting for html/css as well.

Other projects

https://github.com/vitormil/sublime-text-2-preferences/tree/master/HTML-CSS-JS%20Prettify#using-your-own-jsbeautifyrc-options

and

https://github.com/vkadam/grunt-jsbeautifier#default-options-from-js-beautify-can-be-used

Uses one level to first separate html/css/js

Would be great if this structure could be used for this project as well. If doing js-beautify style.css --type css that results in in jsbeautify reading the config file and using what is the js settings for indent etc, not the css settings.

[evocateur]

In my mind, it's a strong argument for spinning off the CSS and HTML beautifiers into separate projects. If the file was named ".beautifyrc", I could definitely see an argument for adding config for different types.

[waynedpj]

Would be great if this structure could be used for this project as well.

👍

[mokkabonna]

@evocateur I would be happy about that as well. Either support html/css fully and make them a first class citizen, like the suggested htm/css/js split of the config file. Or separate them into separate projects and possibly call the files .js/css/htmlbeautifyrc

[bitwiseman]

The discussion of separating the projects is issue #257.

[bitwiseman]

This has been address by having config file with settings per language and inheritance.