Mustafa Taher Ali

Yeah. So my name is Mustafa. I've been, uh, working in Target for now, and I have experience of around more than 6 years. And, uh, I work majorly in front end, and, uh, my experiences lies in React. Js, Next. Js. I work with JavaScript and TypeScript along with other tools, uh, like Redux and all the frameworks that JavaScript has, uh, and React has. I also have ex some experience in Node. Js and MongoDB, though it is not that much. But, uh, yeah, I have experience in that. With, uh, after that, I have experience in GraphQL as well, uh, and Apollo client. Thank you.

This, uh, React Native developer, I haven't worked with. I my experience lies in React JS, not React Native. So, uh, I don't have answer for this.

And so prop drilling props drilling, basically, is that if you have multiple components and those components are in hierarchy, That means, uh, I have a parent component and child component, and the child component has, uh, another child component in with or in to the end of number. So if you want to pass a comp a prop from the grandparent component to a grandchild component, then you'll have to pass it through every component. Right? So that becomes a problem drilling, and that's a big issue because we have to we have to add everything in each component and everywhere a a prop is changed, the whole component, every component gets re rendered. So that is what prop drilling is. It is it is not a best practice. To avoid that, we can use 2 methods. 1 is to create a a a context. So wrap those component in a context, and whatever we have in the parent component can be accessed inside the child component without drilling it. Another one is to create a centralized store like Redux store using Redux or, uh, Redux, DataSaga, or Redux, uh, and, uh, set using that store, we can centralize that data and access everywhere without proctoring it.

There is a function to calculate total amount. K. So we have function b a. Export center tab. Global will be k. And adding text on will be text. Alright. Fine. So, uh, there are some issues in this, uh, function. We already have a row total. So in while adding tax per total, we can just use row total. And the calculation for the amount is not required. And another big issue I find is that there's a there's a hard coded only 3 person bill. And if there's only 2 person, you have to pass. 3rd person is 0 or, uh, yeah, you have to pass it as 0. And if you have only 1 person, then we have to pass person 2 and person 3 as 0. So instead of that, what we can do is we can create, uh, an array of whoever, uh, uh, how however how much people are there. So in that array, we can pass, like, amounts of each person and pass that and calculate inside the, uh, calculate the array inside the function. Uh, with that, we will be able to to accommodate n number of person with the with that amount. Right? And then the load total is 1 plus tax percent. Tax percent is 12%. Addition add in tip will be tip amount. Then first, in this function, our first parameter will be an array of amounts. Then second is text percent and tip. And then, uh, the tax which is adding which is getting added is 1 plus tax percent. That is into 30, which is not correct in this case. Uh, so the formula will be to a percentage, uh, into 100 divided by 100. Sorry. Percent percentage divided by 100 will be added. 1 plus text percent is not right. This is my final answer.

Storage in React Native. Let's define when to user, when to note. Again, uh, no experience in React Native. I thought this this was a React React question questionnaires. But as in storage storage in in React, I can share that, uh, we can use local storage session, storage cache and index DB, and each each serves its own purpose. And, uh, uh, we can use those to persist values, uh, inside the browser and, uh, not not go to server every time and get the data. Just check-in the browser and and get the get the data. Thank you.