Alexey Makhrov

> apparently that won't catch passing null or undefined This is already handled by `strictTemplates` angular compiler setting (in particular, `strictNullInputTypes`) I'm wondering though if adding the input names to...

Any news on that?

The solution proposed in https://github.com/angular/angular/issues/46949 is a run-time check, which is already possible with custom code in ngOnInit. It just abstracts away some repeating boilerplate. What we need though is...

This sounds very valuable for "truely async" observables. However, it's likely to be less helpful on projects using observable state management (eg NGRX), where the state always has some current,...

@tajo @jamiebuilds any feedback on that?

Honestly, the suggested selectMany above doesn't look any better than having 4 individual observables. What would be more helpful though, is creating a single observable view model from that: ```...

Any updates here? I can confirm that realtime messages are not coming for mark_read or mark_seen updates. It makes it impossible to keep an up-to-date notifications counter, without periodically polling...

@freddy38510 any news on that? do you have your changes available anywhere? i'd love to try it on our project and see if it solves the performance issues

I'm seeing 4x-5x faster processing on our typical html page after switching to dropcss-based approach. It's definitely a great boost - but still not sufficient for enabling it in production...

Great question. So when we tried to enable inlineCritical on prod with Angular last time, we got around 500-600ms overhead of pure computations, and it was just too much, we...