Ensure Time.zone.today is evaluated at comparison time #170
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.
Before this commit I think
Time.zone.today
was only being evaluated when the application first booted, rather than each time the validation was called. This manifested as validation error messages for some users when the application hadn't been deployed for several days (e.g. #169).I'm hopeful that passing a lambda to
less_than_or_equal_to
will fix this but I'm unsure of how to express that in a test.Fixes: #169