Advanced Angular tips and tricks

Table of content:
-----------------------------
auto unsubscribe component disposable
auto display component name
pipes programmatically
auto update reactive form inputs
getters in templates
redux dev tools
cmder + cygwin
DI and UI
debug redux
webpack errors
custom form component
blur forwarder
renderer native element
parent change detection
pass data with content children
multi slot transclusion
export as
enums
make dumb components smarter
ngrx side effects
let and forkJoin
cli config
bypass zone
webstorm
faster rendering
trackBy
shared libs
pipe wrapper
app versions
deep css
ngStyle
observer length
ngValue
custom definitions
entry components in modules
store model

Related projects:

[irishpilot]

Nice work,
I do recommend, that, as well as zooming in on the code as you discuss it, (as someone mentioned below) that you change your cursor/Pointer, so we can see it, and Highlight the area you are discussing more often, and take a little more time on the code segment when you are there...By the time I find the code you are talking about, you have moved on...
Thank for the great work.

[imbluedaboodi]

Very insightful. Thank you for sharing. It would be great if you could index the topics however, so we can quickly return to certain sections while coding to explore what you said.

I particularly liked your to-the-point explanation of track-by. The let function of RXJS is also a little gem! I never thought of using it before.

How come we cannot use "export as" for non-directive types?

By the way a beginners dive followed by more indepth aspects concerning change detection and rendering would be invaluable if you have the time one day. The official docs are somewhat unclear.

[chenrvn]

1. Thanks! Very Good stuff! your are rock!
- i learn a lot from that :)

2. There is some stuff that i think break some idea such: simplicity and dependency.
- for example in the section of: "do the dumb component a little bit more smart with the StoreModel", u create a direct dependency in your StoreModel, and thats break the idea of the dumb component, more over it make your test be depend on StoreModel.

3. i see your code and small tip (i am just a guy u know :)):
- clean code: the code need to be more clear from aspect of names, divide your code to more function and then compose them, use more functional way such map and filters...

[ExpeditionCirkus]

A lot of great tips and tricks here, thanks!
Please enlarge the font size next time though since everything is really small and difficult to read. Zooming in (ctrl + '+') should do the trick.

[webzen]

Uh, guys..
addTab(tab: any) {}
Come on.. :D

DO NOT USE :any ! Never!

Thank you, guys, it was interesting video, however, it might raise a lot of questions to your code...

[jafar]

Wish if you had shown in bigger font..!! :)

[anupam.sam]

Way too small fonts... Can't watch. Bye

[edgarsantos]

Sorry mate, can't watch more of the video, had to stop at 18:35. You can't really advertise yourself as a ninja if you don't do the basics, you overuse 'any' which to me I always ask why someone uses typescript if he doesn't care about type check, also you don't explicit return types for methods which it's harder in team work to actually know what something is returning.

Sure you do complex "stuff", and fail on the basics. Ninja you are not, my opinion. Not trying to offend you. Just imagine a Ninja that could fly, but when it comes to punch it would fail.. so no.

I won't dislike the video, or like it.

Great code though!