Miroslav Foltýn

Given that the fix on the surface levels seems to be changing https://github.com/angular/components/blob/5398170c6865d9881162096f2a40b77a74cf3953/src/material/select/select.ts#L1110 and similar cases of handling nulls, are you open for contributions regarding this or is keeping up...

@llorenspujol You can switch from using ContentChild/ContentChildren to query for instances of ktdGridDragHandle to opposite approach of injecting the parent instance of ktd-grid-item into the ktdGridDragHandle through DI and registering...

Similar use case here - have buildable library within NX workspace which I may want to publish for other consumers, the types are mess as well.

Alternatively one could setup routes by providing the ROUTES DI token manually via a factory function. In that factory function you can use inject and hence you can build the...

For such dynamic routes, you may instead want to provide ROUTES token manually through factory function. Refer to provideRouter at https://github.com/angular/angular/blob/d9a1a7dd07497768b1c70fe698b1547bd1f8488e/packages/router/src/provide_router.ts#L90

I see. Perhaps you would be able to get hold of nearest injector through ENVIRONMENT_INITIALIZER like this? https://stackblitz.com/edit/stackblitz-starters-tayqtx?file=src%2Fmain.ts I mean its ugly, but it gets the job done. This isn't...

See https://github.com/angular/angular/issues/54518#issuecomment-1954456046, you don't need to put route subtrees into component providers. Instead, declare them outside the component providers and load just route definitions. I know you have to save...

The problem in your linked [stackblitz](https://stackblitz.com/edit/stackblitz-starters-fjgpj5?file=src%2Flazy-page%2Froutes.ts) is exactly something that the concept in [stackblitz](https://stackblitz.com/edit/stackblitz-starters-tayqtx?file=src%2Fmain.ts) I linked allows you to work around.