Mohammad Mobeen

Yeah. So my name is Maham Navin, and I have overall, uh, 7 to 8 years experience. I started my journey from, uh, PHP, Java, student extended. I have, uh, worked on, you know, corporate sector for, like, 2 to 4 days after that I started working on I started doing the licensing. Uh, for the experience, I have, uh, 6 years experience in PHP and in, uh, I have also experienced with, uh, Angular, approximate, uh, 5 to 6 years. And in Nu, I have 4 years experience. And for the back end languages, I have experienced Laravel, um, Laravel node. And, uh, for the database, MySQL, PostKS, and MongoDB. Uh, what else? Uh, in my recent projects in you, I have worked on a project. Uh, it was a kind of, uh, I mean, the project was called member space where, uh, they have, you know, it's a product where they provide service to the, you know, different, uh, I mean, you know, the the the I don't know what to call them exactly, but, you know, the organization that they the the ones they have, you know, swimming pools where, uh, people come and, you know, uh, join their club. Yeah. Club. And they kind of keep track how many members their club had their club had, you know, and how many members are checking in every day or check out all these things. So, uh, it has, uh, uh, many sections where they are you know, they also have a reporting section where they mail the reports of all the users, billings and everything. Uh, and also they have a 1 section where, you know, they are they they first they are using Mailchimp, but they kind of created their own system using SendGrid. So I did all that. So that was my recent deep projects. Uh, Yeah. That's

Uh, for data transmission, I use, you know, XEO to, uh, communicate between Vue app and REST API. And for securing, I mean, the way I usually do is, you know, I send the JSON format data to the, uh, API and that that, you know, API handles and to kind of, you know, authenticate user if, uh, any user is authenticated to call that request or not. From that, you know, uh, I'll use, uh, token that is provided, uh, while when, you know, you do, uh, logging in the logging, uh, token, uh, mechanism that the way it works is, like, you know, they when you put username and password correctly, and then they, you know, provide you some kind of token that will store in the session or local or cookie storage. And from there, you can, you know, pass that token to the each request that you do after logging. So that's what I know about, you know, sending the data to, uh, REST API and the security

So the state management system is kind of some centralized data, uh, communication like the 1 I mean, like, to put data at 1 place and get data from there. So in order to implement that, first of all, wherever the API is being called, we will need to use, uh, getter and action and, you know, uh, a notation in order to update the data and, you know, call the action to call the API. And after I mean, the APIs will be put in action. And after action, we will need to commit. And, I mean, commit, then it will update the state. And then in that particular component, we will need to use that state in order to bind the data to the, you know, component. The I mean, we will need to do step by step from component to component wherever that API is being used. And if if if there is any child mechanism into that component, for example, if the parent component is calling the API and child components are using those API response, best state management in those child component to, uh, to continue the data flow. For example, you know, if something is passed as a prop to the child component, then we will we won't need to use I think that we won't need to use the prop. We can directly use the state management, uh, I mean, get that all, uh, state on the child company in order to get the data because, you know, whenever data will be mutated to the state, it will be automatically updated on the side. I mean, everywhere wherever the state is used.

Yeah. We'll declare a method creating the widgets directly. That can then play it down based on this scenario. That's 2 player work. So directly we can use the form that will, you know, that if that is handling the, uh, response from the API. So, uh, we normally like if I'm getting the response, like user list or product list. So that will be stored in a global variable in a view, and that variable will be used in a v four, like v four while in data. And then it will be looped through to the particular, you know, div. You can say parent div. And inside that div, there will be child, uh, tags, child elements that will be used to, uh, that will be, you know, used based on the design that we need for the particular section. So that way, it will know the what, uh, what will happen. Unless the API response comes, there will be nothing. Once API response will come, then, you know, it will loop through whatever response we get from the API, then it will, you know, that manipulate the data, uh, along. Or what we can do, we can, you know, put a b and b if to check if there is any data for in particular, uh, element, then, you know, particular section will be shown. Otherwise, it will not. So that way it can

So as far as I understand, the question is like some functionality is already there. And on that particular component, a REST API is being called with particular endpoint, and there is a design based on that endpoint design. So the question is that I need to implement a new functionality, and in that, I need to change the existing endpoint for that particular part of HTML. So in that case, it depends on if the response is similar to the previous response, not all similarity, but, you know, some part of if if some part of it is similar, in that case, I can keep that HTML, which is which has the similarity corresponding to the API response, and I can change the, you know, other part of the HTML that is different for based on the API response. Or if the API response is totally different, then I will need to, uh, I will need to see which part of the estimate is using the API response or which part of the estimate is depending on the API response structure, then I believe I will, you know, uh, um, steal the estimate template based on the new design requirement. For example, if the current, uh, template using table based on the, uh, API response. If it is using table, that means that their response is an array. But if we need to only show the one particular, you know, 1 data or 1 person data in that case, if the design is, you know, table, then I can, you know, I won't need to change much. But if the design is simply, you know, showing the picture and showing the information a user, in that case, table won't be needed, and I will remove the table and create an

Do any JavaScript for this news? Please respond while the data fetch might not be displayed as expected in. Uh, as far as I have used fetch in fetch, we need to kind of use them twice. In first one, we need to kind of return response dot JSON. And in next JSON, we'll see the actual response. So this might create an issue. Other than that, uh, data buttons mounted, which Another thing, it kind of, you know, depends what kind of response we are getting from the API with their design. Array or an object. If it is an object, then it's not going to work at all. It's gonna be. If it is an array, then it might work. But the other one is

In common design for 10 issues, what is it and how does it contribute to the cleaner? I mean, we can do a modular JavaScript. And they are in with we're very clean and, yeah, we can do use multiple

So we can use as far as I know Nuxt. We can, you know, do Nuxt implementation in view. That is the reason Nuxt is used for the view. Uh, for yeah. That that is the one that I know. Uh, for the server side engine, we can use next with view. That, you know, has many options for SEO and all the meta tags that is required for

I have a question, how do you balance the use of third-party VDS plugin with custom component development and continuous create API? For example, it depends what kind of requirement is, if something is kind of little bit complicated and it will take a lot of time if we will, you know, be developing that by ourselves. So in that case, I mean, it's spending that much time on that component, it's better to use third-party. For example, if we need to, you know, use a table where we need to do searching, sorting and filtering. So in that case, we can use a third-party, you know, a third-party plugin or a package like, you know, data table or something, they, I mean, the, and also we need to see if that third-party package is also kind of supportable to the RESTful API, whether it has server-side configuration or not. If it does not have supporting, but it should have something like, you know, to updating the data dynamically to that particular plugin, because the API will take time to respond to the data and after it comes and that particular, whatever plugin I'm using or package that should have the ability to refresh the data whenever, you know, it is provided to them.

Would you approach to what would you approach to be integrate that is what would you Having a type of skill is a very good thing. When first of all, we will need to kind of, you know, write down the configuration to support digestible. And after that we will start, you know, going through component by component or the file by file and, you know, converting that to typescript, converting that code to typescript and, you know, assigning all the types of the variable and responses and everything. And also, FireScape is, uh, you know, very different than JavaScript build JS. We will need to kind of import everything. So that will be kind of anyway hard thing, very complicated kind of thing to do that. If it's, you know, big project, then I will recommend to just do it from press. I mean, it will be kind of doing press. I mean, the, uh, Java skip part, not the single part. Here, we can do this.