Repository navigation
Conversation
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
d484e31 to
29ea269
Compare
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
29ea269 to
7c44826
Compare
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
7c44826 to
ddbe652
Compare
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
ddbe652 to
e2c84c2
Compare
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
There was a problem hiding this comment.
These tests are retained as special handling in the VE compiler was not removed, as it's not currently worth the risk/effort to change VE's behavior.
There was a problem hiding this comment.
This is technically a breaking change (and mentioned in the commit message) to a signature that was not marked as deprecated, but I don't see a different way of achieving this. Since this is test-only code it is unlikely to be called from a library, so I'd consider this an acceptable break.
@atscott This particular change is not accounted for in the fixup commit that removes NgModuleFactoryLoader. Any g3 usages need to be cleaned up separately (or we'd have to extend the patch to undo this change and create an intermediate Injector to provide the given NgModuleFactoryLoader)
There was a problem hiding this comment.
As long as g3 still uses loadChildren: string, we'll still need this because the tests need a way to stub the loader.
Ah, I see what you did. I don't think this should be an issue.
e2c84c2 to
ca967e4
Compare
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
The string syntax for `loadChildren` has been deprecated and is being removed, so this commit refactors the examples to the new syntax.
This commit removes the ability to configure lazy routes using a string for `loadChildren`, together with the supporting classes to load an `NgModuleFactory` at runtime. BREAKING CHANGE: It is no longer possible to use `Route.loadChildren` using a string value. The following supporting classes were removed from `@angular/core`: - `NgModuleFactoryLoader` - `SystemJsNgModuleFactoryLoader` The `@angular/router` package no longer exports these symbols: - `SpyNgModuleFactoryLoader` - `DeprecatedLoadChildren` The signature of the `setupTestingRouter` function from `@angular/core/testing` has been changed to drop its `NgModuleFactoryLoader` parameter, as an argument for that parameter can no longer be created.
Now that `Route.loadChildren` no longer accepts a string, there is no need for tooling to find all string-based `loadChildren` to setup lazy imports for them. As a result, the `listLazyRoutes` operation that enumerates all string-based `loadChildren` occurrences is no longer needed and is therefore removed from the compiler. The `listLazyRoutes` API remains on the `Program` interface to avoid breaking external tools that may be using this method, but those tools should ultimately move away from using this API.
4e54706 to
04fb369
Compare
atscott
left a comment
There was a problem hiding this comment.
reviewed-for: public-api
reviewed-for: size-tracking
|
Pull Approve is confused... |
…3591) This commit removes the ability to configure lazy routes using a string for `loadChildren`, together with the supporting classes to load an `NgModuleFactory` at runtime. BREAKING CHANGE: It is no longer possible to use `Route.loadChildren` using a string value. The following supporting classes were removed from `@angular/core`: - `NgModuleFactoryLoader` - `SystemJsNgModuleFactoryLoader` The `@angular/router` package no longer exports these symbols: - `SpyNgModuleFactoryLoader` - `DeprecatedLoadChildren` The signature of the `setupTestingRouter` function from `@angular/core/testing` has been changed to drop its `NgModuleFactoryLoader` parameter, as an argument for that parameter can no longer be created. PR Close #43591
Now that `Route.loadChildren` no longer accepts a string, there is no need for tooling to find all string-based `loadChildren` to setup lazy imports for them. As a result, the `listLazyRoutes` operation that enumerates all string-based `loadChildren` occurrences is no longer needed and is therefore removed from the compiler. The `listLazyRoutes` API remains on the `Program` interface to avoid breaking external tools that may be using this method, but those tools should ultimately move away from using this API. PR Close #43591
|
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 commit removes the ability to configure lazy routes using a string
for
loadChildren, together with the supporting classes to load anNgModuleFactoryat runtime.BREAKING CHANGE:
It is no longer possible to use
Route.loadChildrenusing a stringvalue. The following supporting classes were removed from
@angular/core:NgModuleFactoryLoaderSystemJsNgModuleFactoryLoaderThe
@angular/routerpackage no longer exports these symbols:SpyNgModuleFactoryLoaderDeprecatedLoadChildrenThe signature of the
setupTestingRouterfunction from@angular/core/testinghas been changed to drop itsNgModuleFactoryLoaderparameter, as an argument for that parameter can no longer be created.
This PR is an alternative to #43575 and removes
NgModuleFactoryLoaderand thestringtype forRoute.loadChildrenaltogether.