Skip to content

Conversation

devversion
Copy link
Member

We need to use "ng_module" for building the keycodes entry-point since we
want metadata to be generated for keycode constants. This is necessary
because some of these constants are statically used in component/directive
metadata (e.g. chips) and NGC needs to be able to evaluate these at compile time.

We need to use "ng_module" for building the `keycodes` entry-point since we
want metadata to be generated for keycode constants. This is necessary
because some of these constants are statically used in component/directive
metadata (e.g. chips) and NGC needs to be able to evaluate these at compile time.
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 25, 2019
@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Sep 25, 2019
@devversion devversion added this to the 9.0.0 milestone Sep 25, 2019
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 Sep 25, 2019
@jelbourn jelbourn merged commit 8584487 into angular:master Sep 25, 2019
andrewseguin pushed a commit that referenced this pull request Sep 30, 2019
We need to use "ng_module" for building the `keycodes` entry-point since we
want metadata to be generated for keycode constants. This is necessary
because some of these constants are statically used in component/directive
metadata (e.g. chips) and NGC needs to be able to evaluate these at compile time.

(cherry picked from commit 8584487)
@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 Oct 26, 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