Skip to content

build: generate a new app in ng new test #27062

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
May 9, 2023

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented May 9, 2023

Currently the ng new integration test uses a pre-generated app which we need to keep up to date. This can cause us to miss changes in the project structure between CLI versions.

These changes switch to generating the project on-the-fly and adding Material to it instead.

I've only done this for the standalone test to verify the approach, but it should be applied to the ng add test as well.

@crisbeto crisbeto 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 May 9, 2023
@angular-robot angular-robot bot added the area: build & ci Related the build and CI infrastructure of the project label May 9, 2023
@crisbeto crisbeto force-pushed the ng-add-standalone-test-rework branch 6 times, most recently from 30af224 to 5143586 Compare May 9, 2023 08:28
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

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

Nice!

Currently the `ng new` integration test uses a pre-generated app which we need to keep up to date. This can cause us to miss changes in the project structure between CLI versions.

These changes switch to generating the project on-the-fly and adding Material to it instead.

I've only done this for the standalone test to verify the approach, but it should be applied to the `ng add` test as well.
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label May 9, 2023
@crisbeto crisbeto force-pushed the ng-add-standalone-test-rework branch from 5143586 to 0f5790c Compare May 9, 2023 10:59
@angular-robot angular-robot bot merged commit 9b0d9fd into angular:main May 9, 2023
angular-robot bot pushed a commit that referenced this pull request May 9, 2023
Currently the `ng new` integration test uses a pre-generated app which we need to keep up to date. This can cause us to miss changes in the project structure between CLI versions.

These changes switch to generating the project on-the-fly and adding Material to it instead.

I've only done this for the standalone test to verify the approach, but it should be applied to the `ng add` test as well.

(cherry picked from commit 9b0d9fd)
@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 Jun 9, 2023
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 area: build & ci Related the build and CI infrastructure of the project 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants