Rubocop always returns an error code (1) instead of a good code (0) so
the beautifier has now been configured to ignore the return code / exit
status for only Rubocop beautifier. Other beautifiers will properly
return error when an bad return code is received.
To switch from `JS Beautify` (CSS) or `Pretty Diff` (SCSS/Sass/LESS) to
using `CSScomb`, you will go into Atom Beautify package settings and
find the option for `Language Config - <Your Desired Language: CSS, etc>
- Default Beautifier` and select `CSScomb`.
CSScomb looks for a `.csscomb.json` file in your Atom's first project
directory. If it does not find one, or if importing it fails, it will
fallback to `csscomb` predefined configuration.
Language config options for:
- disabled - Disable beautifying a language
- `disabled_languages` no longer works
- use the options for each language to disable them
- default_beautifier - Preferred beautifier to use for language
- if there are multiple beautifiers for a language it will choose the
beautifier the user has set as default. Initially the default
beautifier is just the first beautifier to register support for that
language
What's new:
- Beautifier options definition supports:
- boolean - enable/disable
- string - rename and enable
- function - transform and enable
- array - apply complex transformation to multiple options and
output single option result
- Show "Supported by <beautifiers>" for each language option
- Beautifiers have a name
- Beautifier options definition is used to determine if
language option is supported by a beautifier
- Remove SQL test, since sqlformat is inconsistant
Done:
- Create base Beautifier class
- All Languages are separate files
- Options are separated for each language
- Beautifiers reference applicable Languages/Options
- Atom Beautify builds and tests can run
- 19 failures out of 34 tests
TODO:
- Render Language Options to Atom Package Settings
- Support for Language fallback option namespaces
- Support for chosing from multiple applicable beautifiers
Alex Wilson