Kaushal Modi

Hey. Myself, I'm Amundi Koushan, and I'm front end engineer with the VHS. I have a total 7 plus year of experience in the IT field and total 6 plus year of experience with the Vue. Js as a front end engineer. Basically, I have a, uh, work with working experience with the multiple domain, like e commerce, hotel management, SaaS based product, and, uh, HRM based domains. And I have also working experience with the Vue 2, Vue 3, as well as NUC JS for the, um, server side rendering. My working experience with the Vue. Js is like that. I start my journey with the Vue. Js before 6 year. And with my, uh, knowledge and, uh, working experience, I currently am working as a team lead. I have a total 4 member of team and, uh, Vue JS team. As well as I also taking client call, handling client call, getting requirement, and understand debt refinement. And pass to the team, Also, give a deadline of particular projects and task. Also, I give interview for taking, uh, uh, project from the client in the work in IG Shell. So that kind of, uh, work I was done with, uh, my career

Okay. So, uh, for uh, for the risk API and managing data binding to the component, we are used, uh, mounted hook for the calling API and getting the the data based on particular API and bind that data in the component using v model, as well as we can directly bind it that particular data to the data property, and we can manipulate that data in our component.

Okay. So, uh, validate input field, uh, form input field in which is we are used if we are using QSAR, otherwise, we are used, uh, Beautify. And that time that uh, particular frameworks are providing rules for defining validation rules in particular input elements. Okay? As well as we can, uh, define our filter filtration for based on, uh, input value, and we can validate that particular values based on rejects using weighted rejects. Like, we have to all the input number. At that time, we can apply rejects and, uh, uh, take a validation based on

Okay. So, uh, passing data to the API. So for the secure, uh, transmission is dead. We can define, uh, the payload types. And, uh, based on types, we can bind that particular data to the payload for API, uh, API, uh, application. Okay?

Okay. So we can, uh, develop a global component like error error component. So based on that particular API's response, if, uh, we can check that API response is a success or not. Okay? If, uh, API response is not success and it, uh, giving the error, then at that time, we are getting that particular, uh, error message and bind that error message to the global component. Like, uh, we can use that component based on, uh, toast behavior as well as dialogue box, dialogue behavior. That kind of

Okay. For the state management, we can use a VX if we are used of view 2. And we can use if we are used, uh, view 3, uh, v 3. Okay? So based on, uh, state management, we can use a VX, otherwise, So for managing state, we can divide, uh, our state property in VX store. Also, we are mutate and getting, uh, getting that particular, uh, state to the updating behavior. And with the 1, uh, store mechanism, we are defined store name, and we can access that particular store store based on our store name. And we are binding to the API data using the store accents and the mutate that data, uh, to store in state. Okay? So we can easily mutate and manage state in a UX otherwise opinion.

Okay. So Yes. We are defining, uh, one function as a create book, and we are past two parameters. 1 is a title and another reason author. And we are return particular title author and as well as a read, uh, arrow function. Okay? So, uh, in the the create book, we are passed the chemist and, uh, Polo Kolho. Okay? So, uh, my book dot read will be written. Uh, console log is a reading with the title by author. Yes.

Okay? So for the server side rendering, we are use we can use Nuxt. Js because Next. Js is a providing server side rendering mechanism. What is a server side rendering? So core mechanism is that our front end will be, uh, connected to the our server and all the component and the HTMLs are binding from the server, and server will be passed to the front end. Okay? So this mechanism, we can consider as a server side rendering. And for the, uh, SEO, not just is providing SEO, and we can use a header meta type meta to that particular page. And we are defining our keywords for the SEO. So Nudge JS is a better, uh, use for the

Okay. So for the convert migrate JavaScript to TypeScript, then we need to, uh, create a TypeScript files with the dot t s extensions. And, uh, is that, uh, is, uh, very different is very different, uh, for the TypeScript and, uh, the JavaScript mechanism files. Okay? So for the, uh, including TypeScript, we can, uh, use, uh, without changing file, we are defining script. Uh, we are defining language code in the script tag. Okay? So based on script tag, we are defining the language is equal to TS and we can write our typescript code, in particular, uh, GS. So we can easily migrate and to the JavaScript to the type TypeScript. Thank you.

Okay. So for the better offline, uh, technique, you speak in manage our store, uh, with, uh, like, uh, a persistent state. We can use a persistent state of that particular store systems. So we can easily getting data from our local storage and binding that particular data in our front end browser. Okay? So if, uh, we have another Internet service, then it will be easily getting from our local storage. So for that, we are used for distance state of the VX, uh, okay. Thank you.