Varun Mulinti

About your background by giving brief introduction of yourself. Uh, hello. My name is Varun. So I have an experience of almost 5 years in development, uh, working on mostly technologies like Angular, JavaScript, TypeScript. So my previous company was Ivy Comtech. I was a software developer there. I was mostly dealing with the Angular code, the in text tag, Angular code, and dot net c sharp. So that's it.

There are something called auth tokens, basically. Oh, so not sorry. So in Angular, uh, we use something called auth cards where you can check specific rules or specific specific set of, uh, things which you wanna do. Uh, so depending on those, you check the if user have the permissions and not then you authorize specific component of the specific user depending on those routes. So that is how you authorize and handle authorizations in single page applications using Angular. And the same, uh, auth guards, you can put them on the route routing actually to activate the thing. So whenever, uh, whatever, uh, the rule is passed, if the rule is passed, then only the routing link will be accessible to the user. So that is how you manage or handle user authorization in single page applications using Agra.

To implement, uh, optimized, uh, setup animation controller, first thing, then, uh, to control the animations, basically, and then initialize the controller specifying that duration of any optional settings like, uh, v sync, then tick provider. Ticked provider is another thing to ensure the widget implements that the provider, uh, basically to provide vsync. In order to use the vsync, we have to use that. So, uh, then set up animation. Uh, as in using we have to create an animation, uh, by you so that you can apply curves, listeners, and other settings, whichever way we are needed, whichever is whichever thing is required, and then we build the animation depending on that by using animation builder. Then after that, uh, yeah, that's it. Uh, yes.

Lazy loading, we can optimize, uh, the same. And, uh, one is proper dependency injection. Maybe leverage maybe adding angular dependency injection system to provide services in our systematical. You can optimize things. And then, uh, change detection strategy, basically optimizing change detections. Uh, we're using change detection strategy on push or, uh, yeah, on push. So then, uh, then immutable data handling basically, Uh, following mutual principles, uh, when uploading in general, when updating or when playing with the data, updating the states or anything in general to reduce the side effects, basically, uh, and use, uh, we can use, uh, Angular has given a state management libraries like NGRX and RXCS, which makes the developer's life way more easier to handle data, state managements, and data flows. Uh, we can proper usage of input and output, uh, as in the data between parents and child and children using observables or any other way of using RxCS or LinkedIn with the the output and, uh, in general, a direct output and, uh, RxCS in a very good way. So this way, we can, uh, efficiently manage the state management and data flow.

I haven't worked much on testing these things but in my previous company we had this compulsory rule to write test code for whatever things we have done so depending on that experience I'm gonna share my experience basically by using CLI test setup basically where you can test specific test cases and everything and code quality first thing to maintain the code quality in a good way or efficient way I would say and and what else maybe depending on the feature or depending on whatever we are developing develop them in a smaller feature way so that it will be easy to write test cases or we don't miss any other test cases in general to that quite component so that is how I do it and properly injecting dependencies and everything basically that we as in I would say that in general dependency injection plays an important role in these testable test cases or anything ensuring mock dependencies has to be written properly so that is how I do it

Implications of using, uh, NC 2 check as in. Custom change this. If you wanna, basically, uh, it's a n g bootec is a life cycle hook, which comes in the life cycle parts of Angular. So, uh, by using this, you are taking control of the change detections for specific scenarios in general, uh, which we have implemented. So, uh, a few implications has an purpose of using, uh, if you have some logic where you'll have to, uh, detect specific custom logic in general or check something, uh, change something. If there's a change happening and you want to know on that changes, you have to do some particular task, then you have to use n g 2 check. Or, uh, in general, Angular, uh, in changes happens automatically. But if you wanna do it manually, then we use this part of life cycle called n g 2 check. So by not using it, uh, unnecessarily, we can, uh, we can optimize, uh, NG project things and not writing multiple as in complex logics in that method. Uh, so if you what I feel is if you'll write too much logic in that uh, NG 2 check, you are just complicating things for the application. And, uh, it'll be basically, what we use why we use n g two check is to, uh, handle error cases, basically, uh, where not all the other cases, but in general, there are few edge cases where you'll have to handle things using n d n g to check. Uh, that's it.

Let's create a new button and trigger the activated method. Click. Given this angular template, let's explain why the button may not be triggered with the activated method on click. Ok. In this angular template, let's explain why the button may not be triggered with the activated method on click. The way handle click is written, the method in general, it is not in a proper format. As in the syntax way, it is not proper, so that is why it won't trigger the method.

The approach In general, browser compatibility by using Angular, uh, as in there is nothing, uh, different with Angular or any other, uh, this thing. But, uh, so I prefer using I prefer using the media queries mostly to achieve, uh, the compatibility for every browser and uh, every, in general, screen sizes. So there are but still there are few, uh, things which, uh, the application or the browsers won't allow us to implement few things in HTML and few things in CSS as well. So we have to as a developer in general, we have to understand, uh, which browsers, uh, supports what features. So or which browsers does not support what features in general. So that is how I proceed at least. I'll maybe check, uh, the Chrome browser, whichever, uh, style sheet won't work in the whichever or whichever styles won't work in the Chrome that might work in the Firefox or, uh, other browsing browsers, basically. So I would, uh, first check those, and depending on those I write my code, I would try to use, uh, generalized or global format in general. There are always ways to figure out, uh, what to use or what is a global format for that. So I would do that.

This thing. Adding the gesture detection widgets, which are helpful, like gesture detect gesture detectors, uh, and long press tracks in general, like, whatever touch methods are there. Uh, yeah. That's it.

Angular features. How do you angular features? I would, uh, By using maybe a server side rendering, that that thing may affect SEO as well. So by using it, I would improve SEO. Yeah. I would use that, or I would use meta tags and title tags whenever necessary, basically. And, uh, and, uh, server side routing also another thing which can be used to improve the SEO and using lazy load modules, basically, uh, which can improve again SEO. So, um, these things I would, uh, do basically are maybe structured JSON data thing can be used, basically. So the proper structure of the JSON data helps, uh, the helps improve SEO. So that is how I would do in general. So that's it.