-
Notifications
You must be signed in to change notification settings - Fork 78
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
VS-4437: Adding backported functionalities to DatePicker (referenceDate) #821
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- gitignore new line, - readme.md - was importing and using _getAdjustedYear not properly, it was also not conventional, - further fix in parseDate - 30+ tests shall be fixed (Note: only 2 shall remained to be fixed, on it to fix them as well)
…ted tests. - (Asynch tests are right now cannot be added, or at least needed to be transformed, refactored, and tested if this solution is working: Polymer/tools#1302, we need to have a specific version of Polymer as well)
czp13
force-pushed
the
vs-4437-referenc-date
branch
from
January 11, 2023 21:41
395a634
to
2c12c55
Compare
ugur-vaadin
reviewed
Jan 13, 2023
- In the test cases the not used variable is removed, - Added a presentation demo, to show how the reference date is working.
- date-picker-presentation-demos html fixed, used wrong identifiers (the previous example id-s), - _parseDate was not always reachable, now it shall be reachable from vaadin-date-picker-mixin.html always, - 11-31 is not a real date in date picker mixin, so fixed the test.
- Asynch tests reworked (Ugur's idea around were good on assigning i18n values and how to input new values), - Some minor changes were needed around asynchronousity and how to clean the old values when we have embedded test cases, (I spent quite many hours today to figure out, but now all the tests are green, providing proper value) Now all tests are working finally.
czp13
force-pushed
the
vs-4437-referenc-date
branch
from
January 16, 2023 17:45
fcb48e8
to
52b1f5e
Compare
ugur-vaadin
reviewed
Jan 17, 2023
ugur-vaadin
reviewed
Jan 17, 2023
Adding better wording for the new example in presentation-demos.html Co-authored-by: Ugur Saglam <106508695+ugur-vaadin@users.noreply.github.com>
Change Date to date in the presentation-demos.html, as it is more consistent, and follows naming conventions. Co-authored-by: Ugur Saglam <106508695+ugur-vaadin@users.noreply.github.com>
ugur-vaadin
approved these changes
Jan 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The customer agreed to sponsor the reference date feature and backport it from our latest flow-components version:
Related support ticket:
Related GitHub ticket:
The other part of this is at the flow-components:
The issues in the customer's words:
Fixes # (issue)
Type of change
Checklist
Additional for
Feature
type of change