dejanfajfar / epoch.net Goto Github PK

The standard unix timestamp is OK but limited. With its accuracy limitation on seconds this does not provide the accuracy necessary.

For this we should extend the epoch with millisecond.

Certain DateTime dates given to DateTimeExtensions.ToRawEpoch cause integer overflow when converting the TimeSpan.TotalSeconds to an integer.

You'll experience this if you write a unit test with new DateTime(2099, 7, 4, 0, 0, 0). You'll get an output of -2147483648. (The value of TotalSeconds is 4086806400).

When publishing a new package version some additional statistics would be nice. One of those is the code coverage.

When using epoch.net via nuget, the actual usage differs because the compiler gets confused as to the name Epoch being a namespace or a class.

At the top:

After fixing the compilation error:

The incantation of Epoch.net.Epoch is a little verbose due to this namespace and class name clash.

When working with the DateTime class and with JSON Web Tokens, the specification calls for the Unix Epoch to be a double. It would ease use of this nuget package if the API support double for seconds.