for Tracking : day 1 = i learned 1) navigation events 2) passing the data between the components using navigation 3) pipes 4) default pipes and 5) custom pipes filter and percentage 6) pure and impure pipes 7) creating filter and sorting function without using pipes 8) async pipe 9) dynmaic components
Basically whenever we want to open the modal to delete a User we cannot pass the user directly to modal cuz it is out of scope of the loop and we also cant place the modal inside the loop cuz this'd end up creating a modal for each user. What you did was set up a controller flag to tell the model when it should be opened by using the delete method and at the same time selecting and exposing the user that was currently clicked so that the modal has access to it. Nice nice
While practicing this example in angular 17 version, I observed the modal window doesn't show up even though the DOM is updated. (checked the DOM in the browser where the i can see the newly added ng-content related to the confirm-delete window(display:block)), but when i explicitly set the display to block in the .modal css the window shows fine. Could not understand why it is not working as expected with the property assignment and *ngIf. Any idea or anybody has encountered this kind of issue before?
Fabulous series of angular sir..
You can not imagine how this video helped me to get rid of of a lot of doubts I had, thank buddy!
great class
Outstanding video & your explanation sir
for Tracking : day 1 = i learned
1) navigation events
2) passing the data between the components using navigation
3) pipes
4) default pipes and
5) custom pipes filter and percentage
6) pure and impure pipes
7) creating filter and sorting function without using pipes
8) async pipe
9) dynmaic components
Basically whenever we want to open the modal to delete a User we cannot pass the user directly to modal cuz it is out of scope of the loop and we also cant place the modal inside the loop cuz this'd end up creating a modal for each user. What you did was set up a controller flag to tell the model when it should be opened by using the delete method and at the same time selecting and exposing the user that was currently clicked so that the modal has access to it. Nice nice
Please add Angular 17 features.
While practicing this example in angular 17 version, I observed the modal window doesn't show up even though the DOM is updated. (checked the DOM in the browser where the i can see the newly added ng-content related to the confirm-delete window(display:block)), but when i explicitly set the display to block in the .modal css the window shows fine. Could not understand why it is not working as expected with the property assignment and *ngIf. Any idea or anybody has encountered this kind of issue before?
Sir, you miss the lesson regarding routing. Please add one in upcoming days
Next i am going to add Routing lectures.