A key point here, markForCheck method previously didn't trigger change detection it only marks the components as dirty from the current component up to the root parent... but now in Angular 18 besides doing that it also triggers change detection as well... Thats why with signals as well as the Async pipe which call the markForCheck methods are still working properly...
No, markForCheck does the same as before. It marks comp as dirty. It doesn't trigger change detection. Before we used the async pipe, so it would call the markForCheck method, and with signals, we just have to normally call them. Angular now will register an effect (consumer) that will listen to this signal and mark the template for check every time the signal changes. I prepare a big video about change detection. Stay tuned.
@@MonsterlessonsAcademy marking a view dirty does scheduling detection in v18 because of the hybrid CD. The only case where it won't is when opting out of hybrid CD with provideZoneChangeDetection({ ignoreChangesOutsideZone: true }),
Спасибо! Добавь примеров для осталых) по типу - что такое сервисы api - что такое entities и models - как реализовать clean arch or fsd на ангуляр - как пользоваться разумно tanstackQuery без зависимости прямой в шаблонах и features ну в целом приближенный пример production разделения слоев приложения
No it's not. Async pipe specifically is wrapped in mark for check. I will release a video about how change detection workes in Angular soon. Stay tuned.
Do you think Zone.js will be removed in the next version? I always try to keep my teams up to date with new features in their projects, but this time it will be very challenging if we want to switch all our components to OnPush(15 projects in active development). By the way, we haven't had any performance issues, so why is there so much fuss about Zone.js?
I don't know when Zone.js will be removed. As I said Zone.js or Zoneless don't bring performance benefits. Just smaller bundle size and 1 less dependency for the framework itself. onPush brings huge performance benefits. Obviously if you projects relatively simple regarding rendering you might not feel like you need that (but lots of companies forces onPush to all comps by Eslint by default).
Zone.Js won't be going anywhere in the foreseeable future. Too many apps rely on it and it is almost impossible to provide automatic migrations to zoneless.
Can you stop breaking everything, at Google maybe you have one or more developers maintaining an application, in the real world one developer is maintaining 15+ applications!!!!!!!
But nobody forces you to update if you don't need to. I understand the point of backwads compatibility as well as improving performance with signals, zoneless. Angular 18 doesn't have any breaking changes. I don't see the problem.
@@MonsterlessonsAcademy Indeed, I realizei it was created with angular 15 and updated to standalone I made another with newest version and it haas the config file already, thanks a lot!
Most third class framework... No proper documentation, just colorful website. Not given any examples of particular concept, just definition with colorful borders. Matured people will always use React or Vue
@@MonsterlessonsAcademy This is true. But when it comes to developer experience which is the main job of ours, Angular is the worst. No proper documentation on Errors and very less information on APIs. All the time developer has to figure out what is the usage of particular method. Angular team doesn't mentions it. Really disgusting to work with. No offense but this is the reality.
WATCH NEXT: Angular Interview Questions and Answers - Dominate Your Next Interview - ruclips.net/video/5A_YKlVWMPo/видео.htmlsi=2DCn7yspEAAJ2H6l
A key point here, markForCheck method previously didn't trigger change detection it only marks the components as dirty from the current component up to the root parent... but now in Angular 18 besides doing that it also triggers change detection as well...
Thats why with signals as well as the Async pipe which call the markForCheck methods are still working properly...
No, markForCheck does the same as before. It marks comp as dirty. It doesn't trigger change detection.
Before we used the async pipe, so it would call the markForCheck method, and with signals, we just have to normally call them. Angular now will register an effect (consumer) that will listen to this signal and mark the template for check every time the signal changes.
I prepare a big video about change detection. Stay tuned.
@@MonsterlessonsAcademy marking a view dirty does scheduling detection in v18 because of the hybrid CD. The only case where it won't is when opting out of hybrid CD with provideZoneChangeDetection({ ignoreChangesOutsideZone: true }),
Am ready to go zoneless. Need to check if 3rd party components need zonejs. Excellent video thank u!
Good luck!
Since im using signals everywhere i can, I'm cool 😎
Thanks for the video
Yes you are!
Спасибо!
Добавь примеров для осталых) по типу
- что такое сервисы api
- что такое entities и models
- как реализовать clean arch or fsd на ангуляр
- как пользоваться разумно tanstackQuery без зависимости прямой в шаблонах и features
ну в целом приближенный пример production разделения слоев приложения
We already moved to zoneless, it's amazing
Yeap!
maybe its not the async pipe which is triggering the CD, I think its the interval() of the rxjs, it has cd.detectChanges() in it.
No it's not. Async pipe specifically is wrapped in mark for check. I will release a video about how change detection workes in Angular soon. Stay tuned.
Do you think Zone.js will be removed in the next version? I always try to keep my teams up to date with new features in their projects, but this time it will be very challenging if we want to switch all our components to OnPush(15 projects in active development). By the way, we haven't had any performance issues, so why is there so much fuss about Zone.js?
I don't know when Zone.js will be removed. As I said Zone.js or Zoneless don't bring performance benefits. Just smaller bundle size and 1 less dependency for the framework itself.
onPush brings huge performance benefits. Obviously if you projects relatively simple regarding rendering you might not feel like you need that (but lots of companies forces onPush to all comps by Eslint by default).
Zone.Js won't be going anywhere in the foreseeable future. Too many apps rely on it and it is almost impossible to provide automatic migrations to zoneless.
18? wasn't 17 realeased not that long ago ? But thanks for the great Video on it.
It was released at November 8, 2023. Half of the year ago. Time is flying :)
Every 6 months
Angular releases a major version every 6 month. Mai & November usually.
Can you stop breaking everything, at Google maybe you have one or more developers maintaining an application, in the real world one developer is maintaining 15+ applications!!!!!!!
But nobody forces you to update if you don't need to. I understand the point of backwads compatibility as well as improving performance with signals, zoneless. Angular 18 doesn't have any breaking changes. I don't see the problem.
@@MonsterlessonsAcademy of course you don't lol.
@@donwald3436 I don't see the problem neither ..
I'm trying to figure out why my project doesn't have the app.config.ts file 😵💫
It is either older or was generated with modules
@@MonsterlessonsAcademy Indeed, I realizei it was created with angular 15 and updated to standalone
I made another with newest version and it haas the config file already, thanks a lot!
Most third class framework...
No proper documentation, just colorful website. Not given any examples of particular concept, just definition with colorful borders.
Matured people will always use React or Vue
Matured people pick jobs which pay good money and don't care about technologies.
@@MonsterlessonsAcademy This is true. But when it comes to developer experience which is the main job of ours, Angular is the worst. No proper documentation on Errors and very less information on APIs.
All the time developer has to figure out what is the usage of particular method. Angular team doesn't mentions it. Really disgusting to work with.
No offense but this is the reality.
@@4444-c4s On how may projects have you used Angular?
+