In Nswag NodaTime maps ok to at least luxon, if an Instant is used (UTC time).
But if using something like NodaTime LocalDate (which has no time component), I do not see how this could be mapped in a nice way to either luxon or day.js.
@js-joda/core is not as popular as luxon or day.js, but seems like the best match fontend for NodaTime, and has many advantages compared to thoose libraries.
https://www.npmjs.com/package/@js-joda/core
I've managed to configure Nswag to create and parse NodaTime Instant towards Instant in @js-joda/core, but it would be really nice if this was supported "out of the box".
In C# a well used nuget is
NodaTime
. It aims to solve many disadvantages with the built inDateTime
. https://www.nuget.org/packages/NodaTimeThe entity framework data driver
Npgsql
for PostgreSql also suggests to use NodaTime https://www.npgsql.org/efcore/mapping/nodatime.htmlIn Nswag NodaTime maps ok to at least
luxon
, if an Instant is used (UTC time). But if using something like NodaTimeLocalDate
(which has no time component), I do not see how this could be mapped in a nice way to eitherluxon
orday.js
.@js-joda/core
is not as popular asluxon
orday.js
, but seems like the best match fontend for NodaTime, and has many advantages compared to thoose libraries. https://www.npmjs.com/package/@js-joda/coreI've managed to configure Nswag to create and parse
NodaTime
Instant towards Instant in@js-joda/core
, but it would be really nice if this was supported "out of the box".