Skip to content

refactor: move common date input logic into base class #18213

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

Merged
merged 1 commit into from
Jan 21, 2020

Conversation

crisbeto
Copy link
Member

Moves the common logic for a date input into a base class and implements it for the range inputs.

Moves the common logic for a date input into a base class and implements it for the range inputs.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent pr: merge safe labels Jan 19, 2020
@crisbeto crisbeto requested a review from mmalerba as a code owner January 19, 2020 09:20
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 19, 2020
@@ -97,59 +69,17 @@ export class MatDatepickerInputEvent<D> {
},
exportAs: 'matDatepickerInput',
})
export class MatDatepickerInput<D> implements ControlValueAccessor, OnDestroy, Validator {
export class MatDatepickerInput<D> extends MatDatepickerInputBase<D> {
Copy link
Contributor

Choose a reason for hiding this comment

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

Does this need an inputs section in the decorator spec? I noticed that the API goldens show some inputs being removed

Copy link
Member Author

Choose a reason for hiding this comment

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

The inputs got transferred onto the base class, but since it's not exported through the public API it won't show up in the golden. I think the golden only generates code for the class' own fields.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ok, I assumed tests would be broken if those inputs actually got removed, but just wanted to double check.

@mmalerba mmalerba added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Jan 21, 2020
@crisbeto crisbeto merged commit ca03b8f into angular:date-range Jan 21, 2020
crisbeto added a commit that referenced this pull request Jan 24, 2020
Moves the common logic for a date input into a base class and implements it for the range inputs.
crisbeto added a commit to crisbeto/material2 that referenced this pull request Jan 24, 2020
Moves the common logic for a date input into a base class and implements it for the range inputs.
crisbeto added a commit that referenced this pull request Jan 29, 2020
Moves the common logic for a date input into a base class and implements it for the range inputs.
crisbeto added a commit that referenced this pull request Feb 5, 2020
Moves the common logic for a date input into a base class and implements it for the range inputs.
crisbeto added a commit that referenced this pull request Feb 17, 2020
Moves the common logic for a date input into a base class and implements it for the range inputs.
crisbeto added a commit to crisbeto/material2 that referenced this pull request Feb 17, 2020
Moves the common logic for a date input into a base class and implements it for the range inputs.
@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 Feb 21, 2020
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 cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants