Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IS_UTC_DATETIME should not (always) enforce minimum on historic records #1446

Open
nursix opened this issue Jan 31, 2018 · 0 comments
Open

Comments

@nursix
Copy link
Member

nursix commented Jan 31, 2018

In most use-cases it is desirable to be able keep date(time) values when editing historic records.

Those date(time)s would have met the IS_UTC_DATETIME minimum-requirement at the time of entry, but do no longer as time has progressed.

Therefore, the validator should enforce the minimum-requirement only for new entries (unless explicitly configured otherwise).

To achieve that, the validator should have a set_self_id() method. If that method is called with a record ID (which happens during record updates), then the validator instance should suppress subsequent minimum checks.

@nursix nursix self-assigned this Jan 31, 2018
@nursix nursix added this to the 1.1 milestone Dec 5, 2019
@nursix nursix removed their assignment Dec 5, 2019
@nursix nursix removed this from the 1.1 milestone Nov 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant