Skip to content

Conversation

@ncarazon
Copy link
Contributor

  • fixed fatal error on min/max input change
  • adjusted default value for numeric group min/max value

Related to #1448

@ncarazon ncarazon force-pushed the fix/minmax-date-inputs-error-badly-if-you-input-an-invalid-date branch from 1fbde0f to 78c3d03 Compare November 22, 2024 17:14
Copy link
Contributor

@hlbmtc hlbmtc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. But I assume there could be the same issues with DatetimeUtc component.

Also, It could be a good chance to replace datetime-local inputs with DatetimeUtc if this makes sense

@ncarazon ncarazon force-pushed the fix/minmax-date-inputs-error-badly-if-you-input-an-invalid-date branch from 78c3d03 to 49c0465 Compare November 25, 2024 14:39
@ncarazon ncarazon merged commit 035eced into main Nov 25, 2024
2 checks passed
@ncarazon ncarazon deleted the fix/minmax-date-inputs-error-badly-if-you-input-an-invalid-date branch November 25, 2024 15:08
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.

4 participants