Skip to content

Latest commit

 

History

History
150 lines (130 loc) · 8.57 KB

CHANGELOG.md

File metadata and controls

150 lines (130 loc) · 8.57 KB
Raw

1.4.7: 20 Oct 2018

  • Update to version 1.8.8 of js-beautify

1.4.6: 17 Oct 2018

  • Update to version 1.8.7 of js-beautify
  • Add space_after_named_function details

1.4.4: 21 Sep 2018

  • Update to version 1.8.6 of js-beautify
  • Get the tests back to green.

1.4.3: 10 Sep 2018

  • 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

1.4.2: 28 Aug 2018

  • 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

1.3.2: 13 Jun 2018

  • Include scheme (file|untitled) in selectors (Tks @lostintangent)

1.3.1: 11 Jun 2018

  • Improve comment removal for .jsbeautifyrc parser
  • Stop adding extra lines on partial format and format on save

1.3.0: 26 Jan 2018

  • Update to work with multi-root workspaces

1.2.0: 26 Jan 2018

  • Update to version 1.7.5 of js-beautify

1.1.1: 01 Jun 2017

  • Fix the broken things from using the wrong VSCE version to package
    • Adds unindent_chained_methods for js.

1.1.0: 31 May 2017

  • Add ignore option for VS Code formatting
  • Update to version 1.6.14 of js-beautify
    • This adds the void_elements option for html.

1.0.0 - 1.0.2: 20 Mar 2017

  • Update to version 1.6.10 of js-beautify.
    • This returns preserve_newlines for css.
  • Drop trailing comma on schema file
  • Got a new icon, thanks @Slulego
  • Extension is mature enough to go to 1.0
  • Fixed some typos

0.8.0 - 0.8.9: 06 Mar 2017

  • 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 to preserve_newlines have not been changed.
  • Fix preserve_newlines bad interaction with newline_between_rules.
  • Stop deleting text when no beautify type selected when prompted.
  • Update docs for preserve_newlines and file.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 for css.
  • 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 and html parts. A PR has been submitted to schemastore.org which will update and allow the correct seperation of settings once approved.
  • 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 under beautify.config instead of file.
  • Use VS Code file.insertFinalNewLine as root option for end_with_newline.
    • Note: In HTML this is over ridden by html.format.endWithNewline.
  • 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.

0.7.0 - 0.7.5: 13 Feb 2017

  • Fix multiple typos in README (thanks @hubbergit)
  • Bump js-beautify included version after merge of PR#1131
  • Change force-align to force-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.
  • Refactor schema to improve maintainability.

0.6.0 - 0.6.2: 28 Nov 2016

  • 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

0.5.0 - 0.5.5: 16 Nov 2016

  • 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"

0.4.0 - 0.4.1: 15 Oct 2016

  • 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

0.3.0: 03 Oct 2016

  • Add editorconfig as a settings source

0.2.1: 24 Sep 2016

  • 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)

0.1.0 - 0.1.10: 10 Sep 2016

  • 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), and space_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, and html beautifiers to the system range formatters. This means that beautify will run as the system Format code option.

0.0.2 - 0.0.10: 03 Mar 2016