Daniel Scalzi

hopefully they havent changed too much already 😩

Would be great to have this available in the official documentation.

Thanks for this, working great on Node.js 8.x

see https://github.com/FasterXML/jackson-modules-java8/pull/267 for an in-depth explanation. I think these issues are related. In this case you may want to try disabling DeserializationFeature.ADJUST_DATES_TO_CONTEXT_TIME_ZONE. The default timezone in jackson is UTC, and...

Doing some investigating, it seems like this stems from DeserializationFeature.ADJUST_DATES_TO_CONTEXT_TIME_ZONE. When this feature is enabled, the timezone on the resolved ZonedDateTime overrided to be the value of ObjectMapper's set TimeZone....

Further, the output of that depends on the input you pass to `withZoneSameInstant` ```java ZonedDateTime manipulatedUTC = standard.withZoneSameInstant(ZoneId.of("UTC")); System.out.println("UTC Manipulated " + manipulatedUTC.getZone()); // Prints UTC // Resultant ZonedDateTIme would...

Just raised a PR that fixes this issue. I have only investigated this for ZonedDateTimes, as I havent noticed any issues with other java date types.

looking into it

nope, PRs are welcome. My time to go on a forge code hunt is limited.

I18n is not in scope here