Feature 1:
Preferences are now set at the project level instead of being set globally. NOTE: Old global preferences are not being migrated to the project settings so the extension will need to be reconfigured.
Feature 2:
Users can configure the output destination of the minified files by specifying both the source and destination directories.
Bug Fix:
Two related bugs here:
1.) In minifyJsFileOnCommand() (manual minification) the auto-save setting comparison was to "No" instead of "Yes" which meant if auto-save wasn't enable, manual minification would silently fail / do nothing.
2.) If the window is dirty, the manual trigger calls to 'editor.save()' first. If auto-save is set, this save command will trigger saving. It is only when we have just triggered a save that we want to check if auto-save is enabled. In all other cases, we want to minify the files (so the auto-save check was moved inside the dirty-document check).
Feature 1: Preferences are now set at the project level instead of being set globally. NOTE: Old global preferences are not being migrated to the project settings so the extension will need to be reconfigured.
Feature 2: Users can configure the output destination of the minified files by specifying both the source and destination directories.
Bug Fix: Two related bugs here: 1.) In minifyJsFileOnCommand() (manual minification) the auto-save setting comparison was to "No" instead of "Yes" which meant if auto-save wasn't enable, manual minification would silently fail / do nothing. 2.) If the window is dirty, the manual trigger calls to 'editor.save()' first. If auto-save is set, this save command will trigger saving. It is only when we have just triggered a save that we want to check if auto-save is enabled. In all other cases, we want to minify the files (so the auto-save check was moved inside the dirty-document check).