Skip to content

build: moment-adapter package should not depend on all material entry-points #13931

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

Conversation

devversion
Copy link
Member

Since we have the ability to only build specific parts of Material with Bazel, the material-moment-adapter should just depend on it's actual dependencies and not on the whole set of Material entry-points.

…ages

* Since we have the ability to only build specific parts of Material with Bazel, the `material-moment-adapter` should just depend on it's *actual*  dependencies and not on the _whole set_ of Material entry-points.
@devversion devversion added the target: patch This PR is targeted for the next patch release label Nov 1, 2018
@devversion devversion requested a review from mmalerba as a code owner November 1, 2018 18:35
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 1, 2018
Copy link
Member

@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

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Nov 1, 2018
@jelbourn
Copy link
Member

jelbourn commented Nov 1, 2018

This is merge-safe because we don't sync the moment adapter into google
(we have a separate internal adapter for goog.date)

@jelbourn jelbourn merged commit 44a8600 into angular:master Nov 1, 2018
atscott pushed a commit to atscott/components that referenced this pull request Nov 5, 2018
…ages (angular#13931)

Since we have the ability to only build specific parts of Material with Bazel, the `material-moment-adapter` should just depend on it's *actual*  dependencies and not on the _whole set_ of Material entry-points.
jelbourn pushed a commit that referenced this pull request Nov 6, 2018
…ages (#13931)

Since we have the ability to only build specific parts of Material with Bazel, the `material-moment-adapter` should just depend on it's *actual*  dependencies and not on the _whole set_ of Material entry-points.
@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 Sep 10, 2019
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 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