-
Notifications
You must be signed in to change notification settings - Fork 4
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
Allow validating timezone with Inspector calls #831
Conversation
for more information, see https://pre-commit.ci
…urodataWithoutBorders/nwb-guide into inspector-timezone-validation
for more information, see https://pre-commit.ci
…urodataWithoutBorders/nwb-guide into inspector-timezone-validation
Would you recommend this get merged before or after the parent? |
Hmm depends on your answer to this question. With any timezone awareness, we have to decide how we want to limit the user's selection of future dates—if at all. Right now, the date selector uses the current time in local time—but this isn't timezone aware so, for instance, I would not be able to choose a future time tomorrow for a project run in Europe. This is a general problem across both PRs. Though the consequences are limited by Ben's earlier note that data from different timezones will rarely be converted the same day. |
Yeah that's really an edge case so I'll check this out in more detail tomorrow |
Uses NeurodataWithoutBorders/nwbinspector#471 to properly validate timezone with Inspector checks.