- Update to version 1.9.0 of
js-beautify
- Change
beautify.ignore
scope to resource to enable folder configurations in multi-root workspaces to set their own ignored files.
- Add
less
to default configbeautify.language.css
- Fix issue #284 correctly convert VSCode
html.format.extraLiners
- Fix issue # add 'force-expand-multiline', 'aligned-multiple', 'preserve', 'preserve-aligned' options to "wrap_attributes".
- Update to version 1.8.9 of
js-beautify
- Update to version 1.8.8 of
js-beautify
- Update to version 1.8.7 of
js-beautify
- Add
space_after_named_function
details
- Update to version 1.8.6 of
js-beautify
- Get the tests back to green.
- Update to version 1.8.4 of
js-beautify
- Remove settings hints for VS Code settings file. #266
- Honour VS Code html.format.wrapAttributes setting - thanks @admosity
- Clean up Settings.md - thanks @romanrandom
- Update to version 1.8.1 of
js-beautify
- This includes some major change to the HTML beautifier mainly, but includes changes to the CSS and JS beautifiers as well. See the
js-beautify
change log
- This includes some major change to the HTML beautifier mainly, but includes changes to the CSS and JS beautifiers as well. See the
- Include
scheme
(file|untitled) in selectors (Tks @lostintangent)
- Improve comment removal for
.jsbeautifyrc
parser - Stop adding extra lines on partial format and format on save
- Update to work with multi-root workspaces
- Update to version 1.7.5 of
js-beautify
- Fix the broken things from using the wrong VSCE version to package
- Adds
unindent_chained_methods
forjs
.
- Adds
- Add
ignore
option for VS Code formatting - Update to version 1.6.14 of
js-beautify
- This adds the
void_elements
option forhtml
.
- This adds the
- Update to version 1.6.10 of
js-beautify
.- This returns
preserve_newlines
forcss
.
- This returns
- Drop trailing comma on schema file
- Got a new icon, thanks @Slulego
- Extension is mature enough to go to 1.0
- Fixed some typos
- Add multi select format capability.
- Fix bug #106 Copy and paste issue when
formatOnPaste = true
- Update js-beautify version to 1.6.11. This reverts the css
preserve_newlines
option. Work is in progress to fix the bugs. The settings references topreserve_newlines
have not been changed. - Fix
preserve_newlines
bad interaction withnewline_between_rules
. - Stop deleting text when no beautify type selected when prompted.
- Update docs for
preserve_newlines
andfile.insertFinalNewLine
->end_with_newline
- Direct VS Code settings for
config
to updated schemastore.org nested version. - Update to version 1.6.10 of
js-beautify
. - Add
preserve_newlines
to schema forcss
. - Fix
beautify.config
complaining about string (path) value. - Add schema reference for VS Code settings of
beautify.config
.- Note: For now, this will show some out of date settings, and all settings under the root,
js
,css
andhtml
parts. A PR has been submitted to schemastore.org which will update and allow the correct seperation of settings once approved.
- Note: For now, this will show some out of date settings, and all settings under the root,
- Fix default copy of
max_preserve_newlines
from VS Code settings - Fix bug where
beautify.config = null
would cause beautify to clear files when not working within a folder. - Allow
.jsbeautifyrc
settings object underbeautify.config
instead of file. - Use VS Code
file.insertFinalNewLine
as root option forend_with_newline
.- Note: In HTML this is over ridden by
html.format.endWithNewline
.
- Note: In HTML this is over ridden by
- Add config file location setting to VS Code
beautify
settings group. (thanks @IgorNovozhilov)- Note: This is a breaking change, see the README for details on the new
.jsbeautifyrc
search order.
- Note: This is a breaking change, see the README for details on the new
- Fix multiple typos in README (thanks @hubbergit)
- Bump js-beautify included version after merge of PR#1131
- Change
force-align
toforce-aligned
in schema - Fix packaging failure
- Set exact dependency versions (Fix #85)
- Bump js-beautify version to 1.6.8
- Note: This changes the default settings for
"unformatted"
and adds the"content_unformatted"
option.
- Note: This changes the default settings for
- Refactor schema to improve maintainability.
- Force eol to document setting in editor.
- Put back redundant call on save until the textEdit fix is in VS Code (hopefully 1.8.0)
- Remove onSaveIgnore setting as it won't work with the VS Code formatOnSave setting
- Remove redundant format call on save
- Add Settings.md help file
- Change setting retrieval mechanism. Fixes #70 Compatibility with 1.8 Insiders
- Move changelog per VS Code 1.7 workings
- Change icon so it is visible on dark theme
- Add to formatters category
- Add shortcut example (PR #63) Thanks @Tallyb
- Fix VSCode minimum version requirement
- Fix readme typo
- Remove requirement for
beautify.editorconfig
flag - Remove boolean option for
beautify.onSave
in favour of"editor.formatOnSave"
- Stop beautify on save from trying to format unknown types
- Change settings structure
- Reload file association settings when user config is changed
- Allow beautify of (primary) selected lines only
- Add editorconfig as a settings source
- Bump js-beautify version to 1.6.4
- Add non-null defaults for VS Code settings
- Use VS Code format settings as a fallback
- Enable
.jsbeautifyrc
in home drive as a global default - Default format command (Alt+Shift+F) will now work for javascript files (for whole document formatting)
- Fix module structure (again)
- Add sass support explicitly
- Fix beautify on save for JSON
- Improve tests
- Bump js-beautify version to v1.6.3. Adds:
operator_position
(js), andspace_around_selector_separator
(css) - Fix Issue #18: Duplication - same cause as #14 (VS Code changed the way ranges are processed)
- Fix Issue #15: Fail to correctly use workspace setting for file types - introduced in version 0.1.3 (oops)
- Fix Issue #14: Full file beautify doubles text on version 1.1.0
- Add tests for supported formats and nested settings.
- Cosmetic changes to readme/icon
- Beautify with no .jsbeautifyrc file in path tree will use workspace settings for tabs/spaces indent. Issue #11
Will use the editor setting if the file being beautified is visible, or workspace/user setting if it is not visible. (Beautify of a non-visible file can be envoked when beautify on save is enabled.) - Allow beautify on save to work with types in
beautify.*Files
settings. Issue #9 - Fix
beautify.*Files
settings requiring a.
before the extension (both styles are now accepted). - Add beautify on save option. Issue #5: Add Beautify on Save
- Added
css
, andhtml
beautifiers to the system range formatters. This means that beautify will run as the systemFormat code
option.
- Fix typo: Issue #7
- Show info message when VS Code doesn't provide document info and beautify can't run. (Generally caused when file is too large)
- Update js-beautify version to v1.6.2. See js-beautify change log
- Updated schema to match js-beautify v1.6.2 options
- Fix bad type matching when no json schema in user settings.
- Added allowing sub elements in config. Fixes Issue #3: Allow separation of settings for html, css and js options like sublime.
- Changed embedded schema to allow the type sub elements.
- Schema published at http://json.schemastore.org/jsbeautifyrc.
- Added README details for schema install for users of VSCode < v0.10.5
- Added comments remover before JSON parse. Fixes Issue #2: .jsbeautifyrc file not being used
- Changed default (unknown) processing to ask you what you want to use.
- Fixed Issue #1: No handler found for the command: 'HookyQR.beautify'
- Tries to mark any elements in
json.schema
settings as JSON, and thus beautify as JS. - Added schema for
.jsbeautifyrc
file. (Requires VS Code v0.10.5+ see Issue #1) - Added language type so
.jsbeautifyrc
is recognised as JSON. - Add options for other file extensions.