Well, 4747 is really outdated, and it's sad, that the author of this closed it :(
Sad, that he doesn't tag any person, which was merging / reviewing code at the time, or, author of the library :(
I'm gonna try to resolve all conflicts, or, create a new PR, and see, what can be done here

lol, do the @jonrimmer and @jonr-elsewhen are exactly the same person? 🤣

@daniloff200 Almost, one is me at work, one isn't ;-)

Sorry for the circumstances. Our PO decided that this is not important any more after some days of work on it.. Let me know if i can help

hey @juicyarts !
I fixed all the conflicts in your PR, but, there are some test failures, and I'm not 100% sure, how to fix them

Can this be fixed/implemented? Its been a year and a half.

@DanielMcAssey not sure about that right now, we've made a huge reworks during this year and 4747 PR is really abandoned & outdated and requires a big amount of changes

Hey folks. Sorry for this mess. As much as i would like to help out, i'm too far away from angular and this library for some years now and not sure if i will manage to get back into it to finish the ideas from three years ago. I would start a last try this weekend to see if this can be properly migrated and cleaned up in a way that you can at least proceed to finish it. If this does not result in a meaningful outcome i'll get back here next week and inform you. If thats the case i would suggest you don't rely on me for this any longer and start things from scratch.

I added #6322 for the Utc behaviour alignment with the datepicker and juicyarts#1 (based on the utc branch, no MR opened yet) for the offset addition if needed. #4747 was closed in favor of these two branches.

Unfortunately i have a lot of trouble running (all) the tests suites locally so if the general behaviour is what was requested maybe someone else could take over here to add dedicated e2e tests and verifying the unit tests are running as needed. I'm sorry that i can't contribute much more for the time being