montella1507

Well, temporar workarround exists in creation of derived classes for *Control, FormGroup and FormBuilder... however, real solution should be very easy to implement, wonder why it isn't in reactive forms...

Stop crying here.. it will not help with anything... A) do your own extension - it took 2hours to make my own B) use something like https://github.com/ngneat/reactive-forms

> @montella1507 Lol great advice! How dare these developers come here to the issue tracker and report issues! I'm sure your 2 hour extension will solve everyone's issue and force...

@neil-119 same here. 3) is most often not possible 4) not a solution 1) little-bit old-school isnt it? 2) elegant solution - still didnt get a reason for deprecation in...

@Splaktar is there any reason not to use component selector as CSS selector then? something-list.component.ts -> "app-something-list" // components/something-list.scss app-something-list { color: blue; } BTW i think we have the...

Why then just dont use komponent selector as CSS selector then? app-comp1 {}

Can relate. We have only secondary-entry-points for better code-splitting etc. shared/ui - inputs - buttons - etc.. ` ModuleNotFoundError: Module not found: Error: Can't resolve './libs/portal/shared/ui/src/lib' in ` Build error...

Well typical microsoft... They just everyone left behind..

I can confirm this behavior. Workaround is to disable animation with [@.disabled] when RouterNavigationStart (unfortunatelly, you have to DetectChanges manually via CDR) :-/

Wel... i am pretty sure this issue will be closed automatically by NG-bot without being solved.