Set 'actueel' views use now() instead of localtime #243
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The tijdvak is entered in Europe/Amsterdam timezone, so let's make sure that the 'actueel' views make use of the very same time reference.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BAG: De 'actueel' en 'actueelbestaand' views maken nog gebruik van
localtimewat fouten kan veroorzaken als de server in een andere tijdzone staat - zie discussie in issue #223 .In issue #238 is een flinke discussie gevoerd over wel/geen tijdzones te gebruiken. Uiteindeljk is besloten om de Europe/Amsterdam tijdzone aan te houden.