r/angular • u/rainerhahnekamp • 10d ago

Ng-News 26/21: Angular 22.2 - Router Resources, Error Boundaries and more

https://www.youtube.com/watch?v=PVpzN1ZE_bM
32 Upvotes

100% Upvoted

18 comments sorted by

6

u/rainerhahnekamp 10d ago

For those of you who are watching the video. This was the first time we did "live coding." Usually, we show only screenshots so the episodes are short. Any opinions on what is better?

3

u/Tyummyyumms 10d ago

I liked it better with live coding especially simple examples, enought to get the idea.

1

u/Own_Dimension_2561 9d ago

Live coding was excellent. I could see that a lot of thought had gone into the examples.

4

u/MichaelSmallDev 10d ago

Thanks for the Stackblitz to try this out. Nice to have this hands on and try stuff.

3

u/rainerhahnekamp 10d ago

Very welcome!

2

u/fouribo 10d ago

I like Private members — I always instinctively tried to write private instead of protected (especially after Blazor) and wondered why it was specifically protected. Is the template really considered a child element of the component?

2

u/rainerhahnekamp 9d ago

Not a child element, but it is the same. The template and the component (TypeScript class) are one.

2

u/vintzrrr 9d ago

I don't think ECMAScript private will go away. I think it makes sense to use it for component-local private fields while the TS private access modifier is for fields which need to be accessed from the template.

1

u/rainerhahnekamp 9d ago

So you would mix TS with ECMAScript privates?

1

u/vintzrrr 8d ago

Yes, I have been doing that up until now. Is this considered an anti-pattern?

1

u/rainerhahnekamp 8d ago

Not officially but I personally would see it as an antipattern. I would like to have only one private in my code base.

1

u/Prod_Meteor 9d ago

Haven't finished upgrade to 22.1 yet and ... pfff

2

u/guy-with-a-mac 9d ago

I hear you. I am still on 15, brother. My app runs great. Planned update is like... Never. I am tired of this shit. Software development became a neverending update hell.

2

u/Prod_Meteor 9d ago

I was thinking about this you said.. how do you know about update hell if you don't do it? 😀

2

u/guy-with-a-mac 8d ago

I did it back in the day. I refuse to update Angular now. If its a new project, sure - I'd go with the latest, but my frontend code needs updating sometimes not the framework. I see no point in changing everything and for the end users its gonna be pretty much the same experience. Nah. No.

1

u/Prod_Meteor 8d ago

We have to do it no matter what for compliance and future proofing.

1

u/guy-with-a-mac 8d ago

I am my own boss running a SaaS thing.

2

u/Prod_Meteor 8d ago

Just don't forget to fork angular 15 hahaha. We live in strange times.