more than one component, service or directive inside a single file. Every file should be responsible for a single functionality. By doing this, we are keeping our files clean, readable and maintainable.
types immutably, we are preserving the original objects and arrays and modifying only their copies. The easiest way to modify objects and arrays immutably is by using the es6 spread operator (…)
to reference from the template should always have the public access modifier. The private ones will be visible to the HTML template as well, but it is not a good practice due to AoT compilation failure.
should always use the safe navigation operator while accessing a property from an object in a component’s template. If the object is null and we try to access a property, we are going to get an exception. But if we use the save navigation (?) operator, the template will ignore the null value and will access the property once the object is not the null anymore.
benefits like type safety in all the places where you use the action: components, reducers, effects, etc. This might feel a bit weird when you start using it, as one would prefer the less clutter way of factory methods, but using classes will pay off on the long run.
brolag
dropout009
envek
chobishiba
kimura_m_29
ymd65536
tama50505
.jpeg){kind=avatar}
ostk0069
syumai
yjszk
chrisbanes
yoshifumi_ishikura
mototakatsu
iamctodd
csswizardry
notwaldorf
danielanewman
bluesmoon
lara
addyosmani
3n
aleyda
62gerente
carmenintech
denniskardys
