Devesh Pandey

Okay. So I have been working as a web developer, and I am currently posted as Angular developer here at PEER Technologies.

So I have been working. Yeah. State management can definitely be definitely be improved utilizing the TypeScript, type system. basically, by utilizing the type system, we can, keep a handle at what our data type currently is being processed. And after the desired data type of the system is pro is attained, we can move forward with the states.

the best way to integrate rest RESTful APIs are declaration, of services. And, in services, we can write up the functions to, get data, push data, or push data to the RESTful APIs. And further going further into the project, we can call those services and utilize those functions accordingly and at multiple places if we want to.

in Angular, to ensure that the components communicate efficiently, we have to make sure that all the component declarations are clear as can be and the relation of whether they are parent, child, or grandchild have to be declared properly, and, every necessary dependencies have to be called in the in both in the ts file as well as in the

Okay. So for the data binding, first of all, we have to optimize the Angular application's performance. We have to make sure which data or which strand of data is being passed from where, like, from the component to the view or from the view to the component, or either is there a requirement for two way data binding? depending on that, we must ensure the data has been declared in the exact form as for, with the property declare, property binding or with the attribute binding and, if necessary, two way data binding using the NG modules.

basically, the CSS is much preferred to be structured as, from body onwards. If a template is being loaded, the CSS representing the same should be declared in the same component. And, in order to give a higher priority, the CSS must be declared inline and, not, using the n g t property as much as possible.

I suppose. Okay. 1st potential issue that I see is the catch error, block where the error is caught, rather than it being sent to a function to further process or to display, as in the console or for a in or for a inner HTML block. It's been directly sent to some, binding data, like off and so on. And furthermore, after subscribing even, the subscribed item is as it is being, utilized as a variable value for these items.

the main difference that I can find it is if the user rule declared private variable, that is, a string is being manipulated at the same play page multiple same scope multiple times, like after in the get user roles, the after it's been declared as observable, the user roles is being, misassigned the value of the roles and is being returned as it is.

Okay. So first of all, declaring a shared module in Angular that can be lazy loaded across multiple feature modules. Okay. So first of all, we the shared module will be declared out of the scope of all the modules. the means, the app module. it will be declared outside of the scope of it. And, secondly, you will need to call it in, means you will need to call, means, declare the dependency in every ts file or the format that it's gonna be used in. And after doing that for lazy loading, you'll have to whenever you call the services, you'll have to put in a sync and a sync of it log so that for first of all, after we get the services fully loaded, only then will it be loaded into several modules. And the async block would be much better to be, implemented there itself into the service

The constructor. Okay. The pattern that you would use in JavaScript to encapsulate private properties and method. First of all, in Angular, as we know, in constructor, we declare, like, private. And after that, we declare whatever property or method we want to or, in this case, the services. but in JavaScript, there aren't, many of these options, but I'm not familiar with this concept.