Kaushal Modi

Hi, I'm Amundi Koushan, and I'm a front-end engineer with VHS. I have a total of 7 plus years of experience in the IT field and a total of 6 plus years of experience with Vue.js as a front-end engineer. Basically, I have working experience in multiple domains, like e-commerce, hotel management, SaaS-based products, and HRM-based domains. I also have working experience with Vue 2, Vue 3, as well as Nuxt.js for server-side rendering. My experience with Vue.js is like this. I started my journey with Vue.js about 6 years ago. With my knowledge and working experience, I'm currently working as a team lead. I have a team of 4 members, and we're a Vue.js team. I also take client calls, handle client calls, gather requirements, and understand debt refinement. I then pass this on to the team, set deadlines for particular projects and tasks, and give interviews to select projects from clients in the VHS pipeline. This is the kind of work I've done throughout my career.

For the risk API and managing data binding to the component, we use the mounted hook for calling the API and getting the data based on a particular API and bind that data in the component using v-model. We can also directly bind it to the data property, and manipulate that data in our component.

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

Passing data to the API. For secure transmission, it's done. We can define the payload types. And based on types, we can bind that particular data to the payload for the API application.

We can develop a global component that handles errors based on a particular API's response. So, if the API response is not successful and it gives an error, we can get that error message and bind it to the global component. Like, we can use that component based on toast behavior as well as dialogue box behavior.

For the state management, we can use a VX if we're used to view 2. And we can use it if we're used to view 3, v 3. Okay? So based on state management, we can use a VX, otherwise, for managing state, we can divide our state properties into a VX store. Also, we mutate and get that particular state to the updating behavior. And with the store mechanism, we define a store name, and we can access that particular store based on our store name. We bind to the API data using the store and mutate that data to store in state. Okay? So we can easily mutate and manage state in a UX or otherwise opinion.

Okay. So, Yes. We are defining one function as createBook, and we are passing two parameters. One is a title and another is an author. And we are returning particular title, author, and as well as a read arrow function. Okay. So, in the createBook, we are passed the title and author, Polo Kolho. Okay. So, my book dot read will be written. Console log is reading with the title by author. Yes.

Okay? So for the server side rendering, we are using Nuxt.js because Next.js is providing server side rendering mechanism. What is server side rendering? So the core mechanism is that our front end will be connected to our server and all the components and the HTMLs are bound from the server, and the server will pass them to the front end. Okay? So this mechanism, we can consider as server side rendering. And for SEO, it not only provides SEO, and we can use a header meta tag to that particular page. And we are defining our keywords for SEO. So Nuxt.js is a better use for the

So for the convert migrate JavaScript to TypeScript, then we need to create a TypeScript file with the.ts extension. And, is that very different for the TypeScript and JavaScript mechanism files. Okay? So for the including TypeScript, we can use without changing the file, we are defining a script. We are defining the language code in the script tag. Okay? So based on the script tag, we are defining the language as equal to TS and we can write our TypeScript code, in particular, for GS. So we can easily migrate JavaScript to TypeScript.

For better offline technique, you speak in managing our store with a persistent state. We can use a persistent state of that particular store system. So we can easily get data from our local storage and bind that particular data in our frontend browser. Okay? So if we have another internet service, then it will be easily gotten from our local storage. So for that, we are using a detached state of the UX, okay. Thank you.