Skip to content

Conversation

@dimwight
Copy link

Resolves #637

What has been done to verify that this works as intended?

Form defined by datetime637.xlsx reproduces the issue and verifies the fixes.

Why is this the best possible solution? Were any other approaches considered?

Fixes are self-evident?

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

Corrects previous misbehaviour; no regression risk?

Do we need any specific form for testing your changes? If so, please attach one.

As above.

Does this change require updates to documentation? If so, please file an issue here and include the link below.

No?

@dimwight dimwight marked this pull request as draft November 21, 2021 11:06
@dimwight
Copy link
Author

Oops, missed a test that relies on the current code.

@dimwight dimwight marked this pull request as ready for review November 27, 2021 20:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Validation of dateTime widget against now() fails

1 participant