Skip to content

refactor: use light-weight token for form-field in range-picker input#19643

Merged
devversion merged 2 commits intoangular:lightweight-token-optimizationsfrom
devversion:wip/light-weight-tokens-3
Jun 17, 2020
Merged

refactor: use light-weight token for form-field in range-picker input#19643
devversion merged 2 commits intoangular:lightweight-token-optimizationsfrom
devversion:wip/light-weight-tokens-3

Conversation

@devversion
Copy link
Member

The date range picker could be used outside the MatFormField
component in practice. Right now though, the date-picker input
always has a hard-reference on the MatFormField component, causing
it to be retained. This would be the same in View Engine, but with
Ivy this signifies a larger size issue as factories/definitions are
directly attached to the component.

To allow for better tree-shaking / optimizations, we use the form-field
light-weight injection token, so that the date range picker can be used
outside of a form-field with minimal cost.

Related to: #19576.

@devversion devversion added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release labels Jun 15, 2020
@devversion devversion requested a review from a team June 15, 2020 12:50
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jun 15, 2020
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

@crisbeto crisbeto added lgtm action: merge The PR is ready for merge by the caretaker labels Jun 15, 2020
@devversion devversion added the merge: preserve commits When the PR is merged, a rebase and merge should be performed label Jun 15, 2020
Copy link
Contributor

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@devversion devversion added P2 The issue is important to a large percentage of users, with a workaround and removed P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent labels Jun 16, 2020
@devversion devversion force-pushed the wip/light-weight-tokens-3 branch from b7d9b8b to bdf0ce2 Compare June 16, 2020 19:30
The date range picker could be used outside the `MatFormField`
component in practice. Right now though, the date-picker input
always has a hard-reference on the `MatFormField` component, causing
it to be retained. This would be the same in View Engine, but with
Ivy this signifies a larger size issue as factories/definitions are
directly attached to the component.

To allow for better tree-shaking / optimizations, we use the form-field
light-weight injection token, so that the date range picker can be used
outside of a form-field with minimal cost.

Related to: angular#19576.
@devversion devversion force-pushed the wip/light-weight-tokens-3 branch from bdf0ce2 to bd25e46 Compare June 17, 2020 17:10
@devversion devversion changed the base branch from master to lightweight-token-optimizations June 17, 2020 17:10
@devversion devversion merged commit 9bde375 into angular:lightweight-token-optimizations Jun 17, 2020
@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 Jul 18, 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 merge: preserve commits When the PR is merged, a rebase and merge should be performed P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants