Change Log

All notable changes to the "light-switch" extension will be documented in this file.

Check Keep a Changelog for recommendations on how to structure this file.

[0.2.0]

Improved the logic and now allows for proper checking between light and dark hours
Added more unit tests to verify theme switching behaviour
Updated general documentation to improve consistency of the project's codebase.

[0.1.5]

REMOVED: Tests for setTheme.
FIXED: Tests that broke the pipeline.

[0.1.4]

ADDED: Tests for setTheme, switchTheme, workspace.
CHANGED: package.json configuration properties to Dark/Light themes,instead of Night/Day.

[0.1.3]

REVERTED: Test builds to deploy artifacts. Now switching to revising builds with release tags generated by npm version.
CHANGED" patch from the package.json deploy script: vsce publish --yarn.

[0.1.2]

ADDED: Pipeline status badge.
CHANGED: patch to the package.json deploy script: vsce publish patch --yarn
ADDED: Test builds to deploy artifacts.
REMOVED: the information message that printed 'Light Switch is now active!' on activation.
FIXED: Logic for switching themes. It was inverted.

[0.1.1]

Set up an Azure Pipeline following Microsoft's Continuous Integration tutorial.
- PROBLEM: @types/vscode had conflicts with vscode when running yarn test.
  - FIX: Had to remove the old vscode dependency as per the Testing Extension's Migrating from vscode link.
Replaced package-lock.json for yarn.lock.
Updated package.json's compile script to include npm run test-compile, since the ./out/ folder has to be created in order to run tests.

[0.1.0]

Specified default value to "17:00" for lightSwitch.nightTime on package.json — This needed to be done, otherwise it would be "", thus breaking the intended code.
Replaced moment with day.js
Added tests for date validation
Migrated the build to use webpack