[input-date-picker] - Component does not initialize with value.

[richiecarmichael]

Check existing issues

• I have checked for existing issues to avoid duplicates

Actual Behavior

Component does not initialize ISO date. Only place holder text displayed.

          <calcite-input-date-picker
            value={this._departureDate} // "2023-01-01"
          />

Workaround:

          <calcite-input-date-picker
            valueAsDate={toLocalDate(this._departureDate)}
          />

where:

function toLocalDate(utcDate: string): Date {
  const date = new Date(utcDate);
  return new Date(date.getUTCFullYear(), date.getUTCMonth(), date.getUTCDate());
}

Expected Behavior

Expe

Reproduction Sample

None

Reproduction Steps

None

Reproduction Version

1.10.0

Relevant Info

No response

Regression?

No response

Priority impact

p3 - want for upcoming milestone

Impact

No response

Calcite package

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

Esri team

ArcGIS Maps SDK for JavaScript

[maxpatiiuk]

@richiecarmichael is this a duplicate of #7014?

[richiecarmichael]

#7014 is specific to calcite-input-number whereas I'm seeing an issue with calcite-input-date-picker. As @JonUihlein mentioned here the issues may be related. Let's keep this for now. I can assist with verifying/testing when #7014 is fixed.

[jcfranco]

@eriklharper We estimated this at a 5. Do you agree with this or should it be higher/lower?

[geospatialem]

Estimate updated to reflect additional team expertise, which should include updating the tests to allow sending in a full UTC string.

[geospatialem]

Blocked by the effort in PR #8402 to determine if the above is mitigate, or next steps to achieve a solution.

[jcfranco]

@richiecarmichael Would you mind testing this again? It looks like it was fixed in 3.x (thanks for the simplified repro case from #7014, @maxpatiiuk!).

[richiecarmichael]

@richiecarmichael Would you mind testing this again? It looks like it was fixed in 3.x (thanks for the simplified repro case from #7014, @maxpatiiuk!).

Yes, just tested with calcite 3.0.2 and it looks good. Thanks! Closing with bonus points.