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.

Sign up for GitHub

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

Jump to bottom

Cannot set min/max constraints on input with datetime-local type #9281

Open
2 of 6 tasks
nwhittaker opened this issue May 7, 2024 · 1 comment
Open
2 of 6 tasks

Cannot set min/max constraints on input with datetime-local type #9281

nwhittaker opened this issue May 7, 2024 · 1 comment
Labels
0 - new New issues that need assignment. ArcGIS Field Apps Issues logged by ArcGIS Field Apps team members. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. calcite-components Issues specific to the @esri/calcite-components package. impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. spike Issues that cannot be estimated well enough until the team has done further research

Comments

@nwhittaker
Copy link
Contributor

Check existing issues

Actual Behavior

Given a <calcite-input type="datetime-local" /> input, the min/max attributes are unable to be set programmatically due to TypeScript errors. This is because the min/max attributes are typed as numbers.

Expected Behavior

The min/max attributes also accepts strings for constraining a datetime-local value.

Reproduction Sample

https://developers.arcgis.com/calcite-design-system/components/input/

Reproduction Steps

  1. Visit the doc page
  2. Set the type property to datetime-local
  3. Attempt to set the min and max properties to ISO datetime strings

Reproduction Version

2.8.0

Relevant Info

No response

Regression?

No response

Priority impact

p2 - want for current milestone

Impact

The team is looking to use the datetime-local type until #7074 is implemented. In the meantime, it would be beneficial to be able to apply min/max constraints to datetime values.

Calcite package

  • @esri/calcite-components
  • @esri/calcite-components-angular
  • @esri/calcite-components-react
  • @esri/calcite-design-tokens
  • @esri/eslint-plugin-calcite-components

Esri team

ArcGIS Field Apps
@nwhittaker nwhittaker added bug Bug reports for broken functionality. Issues should include a reproduction of the bug. 0 - new New issues that need assignment. needs triage Planning workflow - pending design/dev review. labels May 7, 2024
@github-actions github-actions bot added ArcGIS Field Apps Issues logged by ArcGIS Field Apps team members. calcite-components Issues specific to the @esri/calcite-components package. impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone labels May 7, 2024
@geospatialem geospatialem added spike Issues that cannot be estimated well enough until the team has done further research needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. and removed needs triage Planning workflow - pending design/dev review. labels May 28, 2024
@geospatialem
Copy link
Member

Will investigate further after the efforts of #8126 are implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0 - new New issues that need assignment. ArcGIS Field Apps Issues logged by ArcGIS Field Apps team members. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. calcite-components Issues specific to the @esri/calcite-components package. impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. spike Issues that cannot be estimated well enough until the team has done further research
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nwhittaker @geospatialem