Skip to content

Conversation

devversion
Copy link
Member

In the early stages of the schematics the upgrade data was
stored in .json files. We switched these data files to TypeScript
at some point, but didn't update the schematic-copy glob. Meaning
that we currently ship TypeScript source files within the data/ folder
to NPM for the CDK and Material schematics.

In the early stages of the schematics the upgrade data was
stored in `.json` files. We switched these data files to TypeScript
at some point, but didn't update the schematic-copy glob. Meaning
that we currently ship TypeScript source files within the `data/` folder
to NPM for the CDK and Material schematics.
@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Mar 25, 2019
@devversion devversion requested a review from jelbourn as a code owner March 25, 2019 17:25
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 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 Mar 25, 2019
@jelbourn jelbourn merged commit beae208 into angular:master Mar 26, 2019
jelbourn pushed a commit that referenced this pull request Apr 4, 2019
In the early stages of the schematics the upgrade data was
stored in `.json` files. We switched these data files to TypeScript
at some point, but didn't update the schematic-copy glob. Meaning
that we currently ship TypeScript source files within the `data/` folder
to NPM for the CDK and Material schematics.
@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