Remove Protractor Builder#28632
Conversation
33c80de to
364298d
Compare
…d schematics BREAKING CHANGE: Protractor is no longer supported. Protractor was marked end-of-life in August 2023 (see https://protractortest.org/). Projects still relying on Protractor should consider migrating to another E2E testing framework, several support solid migration paths from Protractor. * https://angular.dev/tools/cli/end-to-end * https://blog.angular.dev/the-state-of-end-to-end-testing-with-angular-d175f751cb9c
…rivate-protractor`
364298d to
2341b36
Compare
|
I patched this change into the FW and Components repos. angular/angular#58254 should be enough to update FW. Components actually doesn't seem to be affected at all. All their Protractor usage comes through Bazel, they don't invoke it through Angular CLI. Once this lands, we should do another |
| @@ -111,7 +111,7 @@ | |||
| "prefix": "", | |||
There was a problem hiding this comment.
Any changes with core can be reverted as this are just test file.
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This renames the Protractor builder and its
e2egenerator schematic to mark them private and remove them from Angular's public API. This will give us an opportunity to clean up internal usages and then remove the builder altogether in a future release. Since this rename makes Protractor non-public API, it may be completely deleted in a future patch release.Protractor was marked end-of-life in August 2023. Projects still relying on Protractor should consider migrating to another E2E testing framework, several support solid migration paths from Protractor.
Additional resources: