Skip to content
This repository has been archived by the owner on Feb 1, 2024. It is now read-only.

Properly call onChange in DatePickerInput #2448

Merged
merged 19 commits into from
Nov 21, 2022
Merged

Properly call onChange in DatePickerInput #2448

merged 19 commits into from
Nov 21, 2022

Conversation

qubis741
Copy link
Contributor

@qubis741 qubis741 commented Nov 16, 2022

Fixed

  • DatePickerInput: overall functionality

Notes:

  • properly call onChange in all cases (onPopover close, as previously it was called multiple times sometimes)
  • fixed displaying of passed error from props
  • if written date is not valid, string is passed in onChange which indicates in our codebase validations that date is not valid

Manuel Check

  • DatePicker story works
  • DatePickerInput story works
  • MC in core with UI library (this PR) connected

@qubis741 qubis741 marked this pull request as ready for review November 18, 2022 16:01
@qubis741 qubis741 self-assigned this Nov 18, 2022
Copy link
Contributor

@eniskraasniqi1 eniskraasniqi1 left a comment

Choose a reason for hiding this comment

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

Checked storybook, looks ok ✅

@qubis741 qubis741 merged commit 7ec493d into next-release Nov 21, 2022
@qubis741 qubis741 deleted the FRAF-1154-v4 branch November 21, 2022 12:05
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants