Skip to content

Conversation

zarend
Copy link
Contributor

@zarend zarend commented Feb 11, 2022

This change only affects the unit tests and doesn't not affect
application code. It's a small improvement to the unit tests in the
multi-year view to use Jan 3 instead of Jan 1. This can catch more bugs
because we could catch that we're setting a date to the first of the
month when we're not supposed to.

This change only affects the unit tests and doesn't not affect
application code. It's a small improvement to the unit tests in the
multi-year view to use Jan 3 instead of Jan 1. This can catch more bugs
because we could catch that we're setting a date to the first of the
month when we're not supposed to.
@zarend zarend added merge safe target: patch This PR is targeted for the next patch release area: material/datepicker labels Feb 11, 2022
@zarend zarend requested a review from mmalerba as a code owner February 11, 2022 00:50
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

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

LGTM

@zarend zarend added the action: merge The PR is ready for merge by the caretaker label Feb 14, 2022
@wagnermaciel wagnermaciel merged commit f0ebd2a into angular:master Feb 15, 2022
wagnermaciel pushed a commit that referenced this pull request Feb 15, 2022
…nth (#24401)

This change only affects the unit tests and doesn't not affect
application code. It's a small improvement to the unit tests in the
multi-year view to use Jan 3 instead of Jan 1. This can catch more bugs
because we could catch that we're setting a date to the first of the
month when we're not supposed to.

(cherry picked from commit f0ebd2a)
zarend added a commit to zarend/components that referenced this pull request Feb 15, 2022
Fixes a failing unit test, which was referencing Jan 1, 2017 as the initial
date when it is actually Jan 3, 2017. This happened as a result of a bad
merge where angular#24384 changed the initial date to Jan 3, and angular#24401 added a
new test that assume the initial date was Jan 1.
zarend added a commit to zarend/components that referenced this pull request Feb 15, 2022
Fixes a failing unit test, which was referencing Jan 1, 2017 as the initial
date when it is actually Jan 3, 2017. This happened as a result of a bad
merge where angular#24384 changed the initial date to Jan 3, and angular#24401 added a
new test that assume the initial date was Jan 1.
zarend added a commit to zarend/components that referenced this pull request Feb 15, 2022
Fix a failing unit test, which was referencing Jan 1, 2017 as the initial
date when it is actually Jan 3, 2017. This happened as a result of a bad
merge where angular#24384 changed the initial date to Jan 3, and angular#24401 added a
new test that assume the initial date was Jan 1.

Fixes CI failure
zarend added a commit that referenced this pull request Feb 15, 2022
…4418)

Fix a failing unit test, which was referencing Jan 1, 2017 as the initial
date when it is actually Jan 3, 2017. This happened as a result of a bad
merge where #24384 changed the initial date to Jan 3, and #24401 added a
new test that assume the initial date was Jan 1.

Fixes CI failure
amysorto pushed a commit to amysorto/components that referenced this pull request Feb 15, 2022
…nth (angular#24401)

This change only affects the unit tests and doesn't not affect
application code. It's a small improvement to the unit tests in the
multi-year view to use Jan 3 instead of Jan 1. This can catch more bugs
because we could catch that we're setting a date to the first of the
month when we're not supposed to.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Mar 18, 2022
@zarend zarend deleted the multi-year-view-unit-tests-first-of-month branch March 29, 2022 22:11
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: material/datepicker target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants