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.

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

fix: ensure DateTimePicker initializes client side value property #2884

Merged
merged 6 commits into from
Mar 18, 2022

Conversation

vursen
Copy link
Contributor

@vursen vursen commented Mar 17, 2022

Description

Fixes DateTimePicker so that it initializes the web component's value property with an empty string rather than leave it to be null when DateTimePicker is being instantiated with no value. This is needed to prevent the value-changed event on the server side which comes from the client side as a result of Polymer converting null to "".

Part of #2691

Type of change

  • Bugfix

Checklist

  • I have read the contribution guide: https://vaadin.com/docs-beta/latest/guide/contributing/overview/
  • I have added a description following the guideline.
  • The issue is created in the corresponding repository and I have referenced it.
  • I have added tests to ensure my change is effective and works as intended.
  • New and existing tests are passing locally with my change.
  • I have performed self-review and corrected misspellings.

@vursen vursen requested a review from sissbruecker March 17, 2022 13:48
@vursen vursen force-pushed the fix/date-time-picker/initial-value branch from bc0dccb to ade6c72 Compare March 18, 2022 07:11
@vursen vursen requested a review from sissbruecker March 18, 2022 07:32
@vursen vursen removed the request for review from sissbruecker March 18, 2022 08:50
@vursen vursen enabled auto-merge (squash) March 18, 2022 08:51
@sissbruecker sissbruecker disabled auto-merge March 18, 2022 08:56
@sissbruecker sissbruecker enabled auto-merge (squash) March 18, 2022 08:56
@CLAassistant
Copy link

CLAassistant commented Mar 18, 2022

CLA assistant check
All committers have signed the CLA.

@sissbruecker sissbruecker merged commit bc8342d into master Mar 18, 2022
@sissbruecker sissbruecker deleted the fix/date-time-picker/initial-value branch March 18, 2022 09:08
vaadin-bot pushed a commit that referenced this pull request Mar 18, 2022
)

* fix: ensure DateTimePicker initializes client side value property

* chore: apply code review suggestions

* chore: run formatter

Co-authored-by: Sascha Ißbrücker <[email protected]>
vaadin-bot pushed a commit that referenced this pull request Mar 18, 2022
)

* fix: ensure DateTimePicker initializes client side value property

* chore: apply code review suggestions

* chore: run formatter

Co-authored-by: Sascha Ißbrücker <[email protected]>
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 841 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

sissbruecker added a commit that referenced this pull request Mar 18, 2022
) (#2893)

* fix: ensure DateTimePicker initializes client side value property

* chore: apply code review suggestions

* chore: run formatter

Co-authored-by: Sascha Ißbrücker <[email protected]>

Co-authored-by: Sergey Vinogradov <[email protected]>
Co-authored-by: Sascha Ißbrücker <[email protected]>
sissbruecker added a commit that referenced this pull request Mar 18, 2022
) (#2894)

* fix: ensure DateTimePicker initializes client side value property

* chore: apply code review suggestions

* chore: run formatter

Co-authored-by: Sascha Ißbrücker <[email protected]>

Co-authored-by: Sergey Vinogradov <[email protected]>
Co-authored-by: Sascha Ißbrücker <[email protected]>
@vaadin-bot
Copy link
Collaborator

This ticket/PR has been released with Vaadin 23.1.0.alpha1 and is also targeting the upcoming stable 23.1.0 version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants