-
Notifications
You must be signed in to change notification settings - Fork 524
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
feat(examples): update angular_bazel_architect to version 11 #2495
feat(examples): update angular_bazel_architect to version 11 #2495
Conversation
dc600cc
to
5a5b04d
Compare
8c9e6aa
to
fc6a31c
Compare
fc6a31c
to
588e9da
Compare
3a9de8d
to
ad615d3
Compare
ad615d3
to
40f5dd3
Compare
03d6c00
to
ea294bd
Compare
ea294bd
to
61c9169
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome 🚀 Reminds me we should update the other Angular example too
Yeah, If I find sometime I'll try to do them in the coming days. |
@@ -4,5 +4,5 @@ import {RouterModule, Routes} from '@angular/router'; | |||
|
|||
const routes: Routes = []; | |||
|
|||
@NgModule({imports: [RouterModule.forRoot(routes)], exports: [RouterModule]}) | |||
@NgModule({imports: [RouterModule.forRoot(routes, { relativeLinkResolution: 'legacy' })], exports: [RouterModule]}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be reverted as there are no routes affected by the related bug IMO.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@saxicek, agreed. Mind opening a PR? thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, opened #2530.
No description provided.