Consider client timezone for deadline validation

[sbacelic]

Should fix issue #40

[prolic]

No on server side we want to store it as UTC. That's why the title is "CLIENT" timezone deadline validation.

[sbacelic]

Got it. I updated pull req.

[coveralls]

Coverage decreased (-0.4%) to 24.504% when pulling ba4a5df on sbacelic:master into 6fba4a7 on prooph:master.

[prolic]

I think the timezone should come from browser, not from php.ini settings. Maybe I am wrong.

@codeliner?

[sbacelic]

Used JS datetime picker is converting deadline to UTC anyway. I'd say store it internally in the UTC, and based on i.e. user's TZ settings (this can be added) render date and time differently.

[prolic]

@codeliner can you take a look into this?

[prolic]

ping @codeliner

[codeliner]

sorry for the delay, I totally missed that issue (sometimes too much is going on on github)

I'm with @prolic The client should send UTC and we take that date and construct the DateTimeImmutable with time zone UTC.

The date picker in the frontend should show local time but store and send UTC. That's the idea of the ticket

[prolic]

ping @sbacelic

[prolic]

nearly one year without activity, closing.