All notable changes to this project will be documented in this file. This project does its best to adhere to Semantic Versioning.
0.12.0 - 2022-01-02
- Update to TypeScript 4.4
0.11.0 - 2021-06-12
- Update to TypeScript 4.3
0.10.0 - 2021-06-05
Dates
andTimestampts
toDisplayTime()
andtoDisplayDateTime()
AM/PM constants change from "a.m." and "p.m." to "am" and "pm" to better align with Javascript defaults- AM/PM constant strings can be change via
DateConstants.AM_STRING
andPM_STRING
0.9.0 - 2020-09-04
- Update to TypeScript 4.0
0.8.5 - 2019-11-08
- Update to TypeScript 3.7
0.8.4 - 2019-07-06
- Update to TypeScript 3.5
0.8.3 - 2018-12-29
- Update to TypeScript 3.2
- Update @types/ dependencies
0.8.2 - 2018-10-17
- Update to TypeScript 3.1
- Update dev dependencies and @types
- Enable
tsconfig.json
strict
- Removed compiled bin tarball in favor of git tags
0.8.1 - 2018-04-14
- Forgot to update package.json version in 0.8.0 release
- Forgot to include release tarball
0.8.0 - 2018-04-09
- Renamed DateTimes.[ts|js] -> index.[ts|js] to follow standard npm package format
- Added release tarball and npm script
build-package
to package.json referencing external process to generate tarball
0.7.5 - 2018-03-31
- Update to TypeScript 2.8
- Update tsconfig.json with
noImplicitReturns: true
andforceConsistentCasingInFileNames: true
0.7.4 - 2018-03-01
- Update to TypeScript 2.7
- Update dependencies: mocha, @types/chai, @types/mocha, @types/node
0.7.3 - 2017-10-14
- New
DateDotNetJson
type (for the formatted strings returned by varioustoDotNetJson()
functions), this is a nominal type based onstring
- Changed the various
parseDotNetjson()
function parameters to accept newDateDotNetJson
type in addition to string tsconfig.json
addednoImplicitAny
,noImplicitThis
, andstrictNullChecks
flags and fixed any related code
0.7.2 - 2017-08-05
- Updated to TypeScript 2.4
0.7.1 - 2017-05-09
- Updated to TypeScript 2.3, add tsconfig.json, use @types/ definitions
- Updated documentation to work better with Visual Studio
0.7.0 - 2017-02-25
- DateConstants MONTHS_SHORT and DAYS_OF_WEEK_SHORT
- Dates.toDisplayTime() and Timestamps.toDisplayTime()
- DateUtil.isSameDate()
- DateTimes.DateUtil
- Renamed DateUtil getTimeSince() to getMillisSince()
0.6.0 - 2016-12-31
- TimestampUtc better nominal type behavior, changed from an
interface
to atype
which auto down-casts tonumber
, but must be explicitly cast to.
0.5.0 - 2016-12-21
- TimestampUtc interface now extends Number and has a marker property so that it behaves as a strong type
0.4.1 - 2016-11-07
- toDotNetJson() to handle date.getTime() returning a TimestampUtc
0.4.0 - 2016-11-05
Some method documentation
- DotNetJsonDate:
- parseDotNetJson() now throws an error when a null or empty argument is passed in
- toDotNetJson() now throws an error if the date argument is null or invalid
- Timestamps
- toDotNetJson() defaults to 0 if the timestamp argument is null instead of the current date
- Small unit tests update
0.3.0 - 2016-10-22
- DateConstants MILLIS_PER_WEEK, MONTHS (string array of full names), DAYS_OF_WEEK (string array of full names)
- DateUtil class with methods like getTimeSince(), isBefore(), getWeekInYear(), getPreviousSunday(), etc.
- Renamed DateConstants MS_PER_DAY -> MILLIS_PER_DAY
0.2.0 - 2016-10-08
Major refactoring, split DateTimes into:
- Dates, Timestamps, DotNetJsonDate
- Removed timezone related parameters from timestamp/dotNetJson methods since these methods should handle timezone automatically and Javascript's Date.now() and getTime() are implicitly UTC which I didn't clearly understand until now
0.1.2 - 2016-09-17
- Forgot a few changes in the last commit for handling TimestampUtc
0.1.1 - 2016-09-17
- Timestamps module with utilties for dealing with TimestampUtc including duplicates of DateTimes.Timestamp currentTimezoneOffsetMillis, now(), and toDate()
0.1.0 - 2016-08-28
Initial commit of existing DateTimes module moved from ts-mortar project