fix(webapp): event date format

[Mogge]

🍰 Pullrequest

Issues

• fixes 🐛 [Bug] Events – On set Event Filter an Event of the same Day is not Visible #6783

Todo

• migration to fix dates on server

[Tirokk]

Do we need a migration of the DB? @Mogge

[Tirokk]

That does work on Safari and Firefox. 👍🏼

[Tirokk]

• care for the summer and winter time @ulfgebhardt
  • may we can use the creation date to distinguish between it?
  • !!! we decided to set winter time in the migration !!!
• give a backend error if the frontend sends not UTC datetime? @Mogge

[ulfgebhardt]

I think we should define a time before this transformation happens and one after this will not happen.
if(post.createdAt is before XXX)

If we should do the extra effort to calculate the summer and winter offset is not important to me.

I do not fully understand if the problem is solved with the Conversion to Date - i assume it takes the given timezone and converts it to UTC, but thats an assumption.

[Tirokk]

Works excelent. @Mogge

Therefore I approve 🚀🚀💫💫

PS: I tested the error message in the browser as well. Cool! 😍
PPS: And you already corrected the hour offset. 👍🏼

[Tirokk]

!!! Before we merge we have to prepare the stage.yunite.me to test the migration on the server !!!

[Tirokk]

A very good idea to take the migration out of the coverage. 👍🏼

[Tirokk]

!!! Before we merge we have to prepare the stage.yunite.me to test the migration on the server !!!

[Tirokk]

Test migration on stage.yunite.me by:

• removing the automatic seeding in publish
• entering the database cypher shell via Kubernetes
• run the folling commands before and after merging this PR into the master and auto deployment:

MATCH (event:Event) WHERE NOT event.eventStart CONTAINS 'T' RETURN event.id, event.eventStart, event.eventEnd;

Or:

MATCH (event:Event) RETURN event.id, event.eventStart, event.eventEnd;