Why do you add an 'interface' postfix in interface? You don't add a 'number' postfix when creating a variable with type number for example, so what's the reason to do this with interfaces and types?
At GoodTableComponent, won't be better to set the issueSig with a @Input() set instead of doing it inside the OnInit? @Input({ required: true }) set issues(issues: IssueInterface[]) { this.issuesSig.set(issues); }
Hello, When you create a ngclass to control if is selected or not (minute 12), would be better to use ngclass (something like 'issue.id.isSelected: selected') and create a css class to change color? Great video as always, keep the good work. Thanks
You can compute signals from inputs if you provide them as input signals. This is quite the new feature though, is that the reason you're not covering it here?
Why you do not create an IssueClass that implements the IssueInterface and extends it with a "selected" property? Then, in the view, simply change item.selected to true without requiring an additional array for selected elements. To obtain the count of selected elements, you can filter the array of IssueClass elements by the selected field and count the results.
I don't like to mix view logic and entity. As we don't get isSelected through input we must say that we got IssueInterface and not extended version. Then anyway you need to transform your data type to data type with isSelected.
Good. But you are still writing angular code with a react background. You refactor can be easly refactor in an half of code by an angular senior developer who realy knows the angular api.
@MonsterlessonsAcademy use a set input to set a signal to cover the ngOnChange. Try to use only computed signal as much as possible to leep one sources of data. Use the formControl api instead of your change event from your checkbox. Utilise the power of rxjs to handle your event logic and convert it to signal in your constructor if you need a signal output (to display the result in your view in a prevision of signal baswd component). Don't use ngClass if you only have one condition. [Class.myClass]="condition" is a nicer way to handle it. Don't use *ngFor/*ngIf which is the "old" syntaxes. If you are in 17.* you should have access to the new template syntaxes.
@@MonsterlessonsAcademy Just one thing I wanted to ask. In the video you converted the @Input() to signal. Is it also possible to have the issues property be a signal, eliminating the need for converting from @Input to signal?
@@MonsterlessonsAcademy Exactly. Since I have watched your videos about implementing components without libs. So maybe you can create sth about using CDK to create compoents?
When I hear this is Junior level Code I feel offended being considered Junior after now 7 months into the job. I agree that this code is really super bad.
WATCH NEXT: Angular Interview Questions and Answers - Dominate Your Next Interview - ua-cam.com/video/5A_YKlVWMPo/v-deo.htmlsi=2DCn7yspEAAJ2H6l
Absolutely amazing man , been following since 2021 , still the same humble teacher!
Glad to hear that!
Why do you add an 'interface' postfix in interface? You don't add a 'number' postfix when creating a variable with type number for example, so what's the reason to do this with interfaces and types?
It is easier to separate a class from the interface or type in a big project. What's the reason to name a component in Angular FooComponent ?
At GoodTableComponent, won't be better to set the issueSig with a @Input() set instead of doing it inside the OnInit?
@Input({ required: true }) set issues(issues: IssueInterface[]) {
this.issuesSig.set(issues);
}
Yeap or we could use input signal. I always forget about new Angular features while coding.
amazing!
U r awesome!
I always learn with u. Thank you
My pleasure 😊
Hello,
When you create a ngclass to control if is selected or not (minute 12), would be better to use ngclass (something like 'issue.id.isSelected: selected') and create a css class to change color?
Great video as always, keep the good work.
Thanks
It's more a matter of taste. This is just 1 line of code. If we had more styles than sure.
You can compute signals from inputs if you provide them as input signals. This is quite the new feature though, is that the reason you're not covering it here?
Was also wondering this
I didn't use them in the video as they are in developer preview. Sure you can do that.
@@MonsterlessonsAcademy Ah I see. We already use them heavily in our project and they work flawlessly :)
This is pure gold!! Thanks
Thank you!
What I would also do is place open and resolved statuses to enum
Yeap, thats a good idea.
So junior code turned into "senior junior" one. Now need to call middle guy to upgrade this.
This is very helpful thank you for sharing!
Glad it was helpful!
Why you do not create an IssueClass that implements the IssueInterface and extends it with a "selected" property? Then, in the view, simply change item.selected to true without requiring an additional array for selected elements. To obtain the count of selected elements, you can filter the array of IssueClass elements by the selected field and count the results.
I don't like to mix view logic and entity. As we don't get isSelected through input we must say that we got IssueInterface and not extended version. Then anyway you need to transform your data type to data type with isSelected.
If our version of angular less than 16 we can initialize input array like empty array in order to avoid non-null assertion
Yeah, or think about project upgrading -_-
Can you Videos zu best structure folder files for big project
I covered the folder structure for React. It is the same for any framework
ua-cam.com/video/IFTqfO_evlc/v-deo.htmlsi=1-QaWl1AdMq1fjts
When I see suffix *Interface in an interface name I'm thinking that it is a beginner code
Sounds like a good indicator of junior code.
Good. But you are still writing angular code with a react background. You refactor can be easly refactor in an half of code by an angular senior developer who realy knows the angular api.
What do you mean?
@MonsterlessonsAcademy use a set input to set a signal to cover the ngOnChange. Try to use only computed signal as much as possible to leep one sources of data. Use the formControl api instead of your change event from your checkbox. Utilise the power of rxjs to handle your event logic and convert it to signal in your constructor if you need a signal output (to display the result in your view in a prevision of signal baswd component). Don't use ngClass if you only have one condition. [Class.myClass]="condition" is a nicer way to handle it. Don't use *ngFor/*ngIf which is the "old" syntaxes. If you are in 17.* you should have access to the new template syntaxes.
Signals are so awesome. Thanks for the this informative video, will definitely be using signals more often now.
Glad it was helpful!
@@MonsterlessonsAcademy Just one thing I wanted to ask. In the video you converted the @Input() to signal. Is it also possible to have the issues property be a signal, eliminating the need for converting from @Input to signal?
Signals make everything so easy :D
Yeap
You are my most favorite Angular teacher.
Wow, thanks!
Do you have plans for creating a series of Angular CDK tutorial?
Not really but I will add it to the list of ideas. You mean Angular Material CDK?
@@MonsterlessonsAcademy Exactly. Since I have watched your videos about implementing components without libs. So maybe you can create sth about using CDK to create compoents?
@@ARShindouAR I will add it to the list of ideas
this video is so helpful
Glad you like it!
Amazing, thanks
Thank you too!
Great one!
Thanks!
Thanks
You are welcome!
Awesome as always
Thank you so much 😀
When I hear this is Junior level Code I feel offended being considered Junior after now 7 months into the job. I agree that this code is really super bad.
Yeap