I like that this clearly describes the action as an independent thing to describe what happened, and that the reducer responds to it on its own - the action is not commanding anything, it's just an event. And I like that you colocated the state files with the features they were relevant to instead of in a big centralized folder.
wow awesome video .....i have learn a lot...i have save my expensive also . i thought i have buy udemy but this series is more helpfull...thanks for your hardwork.
Hi it's a good tutorial as an intro to ngrx. But if i may i will add one suggestion : please explain more what you are typing because as an introduction people won't probably understand why for example you type " this.store.subscribe(state => (this.customers = state.customers.customers));" It is quite important for the beginners to explain the mechanism behind the techno. Beside that, keep the good work :)
As a beginner, I am not able to understand how this.store.dispatch({type:'LOAD_CUSTOMER'}); from list component called the reducer. Is this any redux property or what?
error TS1312: Did you mean to use a ':'? An '=' can only follow a property name when the containing object literal is part of a destructuring pattern, Error: ./src/app/customers/state/customer.reducer.ts 2:14 [0] Module parse failed: Shorthand property assignments are valid only in destructuring patterns (2:14) [0] File was processed with these loaders: [0] * ./node_modules/@angular-devkit/build-angular/src/babel/webpack-loader.js [0] * ./node_modules/@ngtools/webpack/src/ivy/index.js [0] You may need an additional loader to handle the result of these loaders.
Another suggestion, there is the craze of, first explaining the steps we must follow, and at the end we see the result, for me, and I think for everybody results more understandable, first of all explain the objective. I mean for example in this video: Objective: We are going to prepare our first action and reducer and this action and reducer will show us the list of customers. Then after that, keep the explanation you gave, almost exactly like it is. I say this because, when i try to learn from this videos, normally, I "loose my tracking" of hat I am doing, so just get to follow a bunch of steps without meaning in my head, finally, some result is got, but... the bi group of steps is impossible to be remembered in the right order, or completely or... something goes wrong always cause, meaningless thing are imposible to remember right. So begining by just telling your intention gives some shape to all the actions you are going to perform. Do this make some sense?
In 4th video while u r subscribing to store in CustomerList Component u need to explain why you are using stste.customers.customers for beginners i guess. Very less explanation and typings can also be added
I like that this clearly describes the action as an independent thing to describe what happened, and that the reducer responds to it on its own - the action is not commanding anything, it's just an event. And I like that you colocated the state files with the features they were relevant to instead of in a big centralized folder.
wow awesome video .....i have learn a lot...i have save my expensive also . i thought i have buy udemy but this series is more helpfull...thanks for your hardwork.
Hi it's a good tutorial as an intro to ngrx. But if i may i will add one suggestion : please explain more what you are typing because as an introduction people won't probably understand why for example you type " this.store.subscribe(state => (this.customers = state.customers.customers));" It is quite important for the beginners to explain the mechanism behind the techno. Beside that, keep the good work :)
Thanks for the suggestion. I understand NgRx is a confusing topic for a beginner. I'll keep that in mind for future videos.
As a beginner, I am not able to understand how this.store.dispatch({type:'LOAD_CUSTOMER'}); from list component called the reducer. Is this any redux property or what?
@@iamitsingh yes, dispatch is a redux method that calls the customerReducer function.
greate content
good presentation
error TS1312: Did you mean to use a ':'? An '=' can only follow a property name when the containing object literal is part of a destructuring pattern,
Error: ./src/app/customers/state/customer.reducer.ts 2:14
[0] Module parse failed: Shorthand property assignments are valid only in destructuring patterns (2:14)
[0] File was processed with these loaders:
[0] * ./node_modules/@angular-devkit/build-angular/src/babel/webpack-loader.js
[0] * ./node_modules/@ngtools/webpack/src/ivy/index.js
[0] You may need an additional loader to handle the result of these loaders.
Another suggestion, there is the craze of, first explaining the steps we must follow, and at the end we see the result, for me, and I think for everybody results more understandable, first of all explain the objective. I mean for example in this video:
Objective: We are going to prepare our first action and reducer and this action and reducer will show us the list of customers. Then after that, keep the explanation you gave, almost exactly like it is.
I say this because, when i try to learn from this videos, normally, I "loose my tracking" of hat I am doing, so just get to follow a bunch of steps without meaning in my head, finally, some result is got, but... the bi group of steps is impossible to be remembered in the right order, or completely or... something goes wrong always cause, meaningless thing are imposible to remember right. So begining by just telling your intention gives some shape to all the actions you are going to perform.
Do this make some sense?
for what do you need loaded and loading property? when do I use it?
Thank you bro!!!
nice video.
on compilation it throws errror - ERROR in src/app/customers/customers.module.ts(6,33): error TS2307: Cannot find module './state/customer.reducer'
Where is the action?
In 4th video while u r subscribing to store in CustomerList Component u need to explain why you are using stste.customers.customers for beginners i guess. Very less explanation and typings can also be added
jaja yes, it's because of the parent folder name of the store of that module