Skip to content
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

chrore(ng-schematics): Update ng e2e to custom builder #9300

Merged
merged 4 commits into from Nov 22, 2022

Conversation

Lightning00Blade
Copy link
Collaborator

What kind of change does this PR introduce?

This replaces the default ng e2e with our custom builder. In the feature it seem possible to remove the necessity of the user running the server separately and run it from the builder - that will improve the easy of use and CI of this schematic.

Did you add tests for your changes?

If relevant, did you update the documentation?

Yes - Updated @puppeteer/ng-schematics README.md

Summary

We want to not see the default ng e2e and we want to make it easier for the user to run commands.
Angular Developer are likely to also use its' CLI.

Does this PR introduce a breaking change?

Yes. Users need to delete the default and initialize the schematics again.

Other information

@Lightning00Blade Lightning00Blade merged commit 4613f03 into main Nov 22, 2022
@Lightning00Blade Lightning00Blade deleted the feat/ng-shematics-replace-ng-e2e branch November 22, 2022 13:02
OrKoN pushed a commit that referenced this pull request Nov 22, 2022
**What kind of change does this PR introduce?**

This replaces the default `ng e2e` with our custom builder. In the
feature it seem possible to remove the necessity of the user running the
server separately and run it from the builder - that will improve the
easy of use and CI of this schematic.

**Did you add tests for your changes?**

**If relevant, did you update the documentation?**

Yes - Updated `@puppeteer/ng-schematics` README.md

**Summary**

We want to not see the default `ng e2e` and we want to make it easier
for the user to run commands.
Angular Developer are likely to also use its' CLI.

**Does this PR introduce a breaking change?**

Yes. Users need to delete the default and initialize the schematics
again.

**Other information**
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants