It's maybe one of those tricky issues, that's only an issue temporarily in those odd 'gap hours', because my first re-production didn't yield the same issue:

Time of writing is 29th of september, at 10:50, so 1st of september is in "two days".

Will try and reproduce by overwriting the data payloads in network tab of developer tools :)

I was able to reproduce the error, by using a chrome extension for 'time traveling' to late in a day, and if today is 22:57, then the milestone that's technically two days later will show as 'tomorrow'!

Getting closer.

Oh, it's not a timezone thing.

If there's 24 hours or more, then it will say two days. If it's 23 hours and 59 minutes, it will say 1 day.

To be continued ...

{
      field: 'nextMilestoneDeadline',
      renderCell: (params) =>
        params.value ? (
          <ZUIRelativeTime datetime={'00:00 10-01-2024' as string} />
        ) : null,
        

This is showing as tomorrow, while 00:01 is in two days oOOoo

@Idkirsch and I tried, but failed :'(

But we had fun hehehehehe

I think it's something in the react-intl library think that the best format for all times between now and 23 hours and 29 minutes and 59 seconds into the future should be formatted as ex. "in 23 hours", but higher until 1 day and 11:59 later become "tomorrow", then until 2 days and 11:59 it says "in 2 days" etc. (based on some tests, didn't check their code.)

In my mind it would make more sense to also consider the current time, ex. if the time is 20:00 then anything higher than 4 hours is "tomorrow" OR anything between 24 and 28 hours is tomorrow, etc. I don't see any obvious way to do this in their docs, but I think they use a (poly filled?) version of Intl.RelativeTimeFormat. Maybe <ZUIRelativeTime/> could be implemented using this directly without react-intl? Unless there's somewhere else where their idea of formatted relative time makes more sense.

I'm open for spending some time later this week if you this sounds reasonable.

(I also spent enough time on Saturday to get annoyed that it didn't get a solution, so looked some more this evening.)

@Herover @Idkirsch @troldmand I love all the explorations you have done of this! So frustrating that you didn't find a solution over the weekend, but as you probably know, every time you research or attempt to solve time related bugs a magical koala baby gets its wings 🐨 🦄 🪽

@Herover go for it! I think your ideas sound cool!

Thanks @ziggabyte, and go nuts @Herover. Maybe @Idkirsch and I would also look into another fix on Thursday ☮️ we will post her before picking up any work, hope you will the same @Herover 🤙

We have a patch for this now! :) But it could be improved, see the review comment on the PR.