Shivam Mishra

My name is. Uh, so I have, like, 3 years of experience in the mindset. So I started working for a new startup. Actually, startup in there, I worked for, like, around 2 years and 5 or 6 months. And then, uh, I'm not more mainly as a full stack developer in the money stack. Um, so Uh, right now, I'm working for another startup, uh, media music, and have to, uh, create the

So fragments. So So basically what happens in reactive like if you have multiple children, it should be wrapped inside the parent children or parent element. So you cannot render multiple changes without running time. So in those cases, you will be using fragment because there's no point using a a div element there because, um, it will run necessarily there in the DOM. So yeah, it will handle the fragments and it will it will not be there in the real

Uh, so basically, uh, you can have Uh, from somewhere in the user tag. So what we can do is have a state. So once the data is available,

So first thing I the this all the states, and then move to, uh, the u b state in the functional component. So the render function in the, uh, render method in the process component will be the written part of the, whatever in the 2010s will be dependent as part of the function component. And other than that, like, if you have So life cycle, it's like, uh, subcomponent update, bit component update,

The key component will be the, uh, where are we going to use that step? For example, if that is the company in some multiple places. Uh, then I think I will put it in the global states because global state was, uh, it's going to be used in new places. Um, otherwise, if it is just being trying to be used in a particular component, for example, if it is a UI state, then I will try to Oh, that is getting the component itself and not in the, uh, uh, global state. So for any data that is coming from server side or any data that is being used in multiple components including the local state, And if I have some, let's say, some data or so I will fetch it from fetch it and store it, uh, it in the maybe in data State order. This will be a global state. Maybe in some context some state, and I will, uh,

So, uh, I will handle the error, uh, in the case block. Obviously, I will have the try case block. So I will handle the error in the case. I mean, uh, case data the the chatbot and then I will update the state that there wasn't I mean, let's say I have some state called the status. Error.

Uh, one problem here is to when we are doing the we are when in our understanding, we are not getting the data from the Uh, element being written from the render method. So it's just telling that we sort of state of that, which is not fine. Uh, so I don't know whether this sender is just for example. I don't know. But The handle is definitely not, uh, the way it should be because you can it it's just hard pulling the hello world every time. It's not being changed, uh, on when we could change So I would say you should have an input element and every time and put an on change listener there and then, Put the handle change there. Handle change will get an event as a as a parameter for argument, and then you can put the put the event of target dot value. And also put the value so it made the input as controller compliant so that, uh

Uh, in the AS, maybe you cannot return text like this. So the AS method has some set of components like, new text. Uh, so everything has to be inside those native components. For example, you cannot put the text hello world directly there like this. You have to put it inside the text text component. Once you put it in the text component, it should work. Also, your the styles that we are having is not in utero. So maybe if you want to have some styles, you can put the view component and inside you can have the text. So your container style will go in the view and then, uh, inside text will uh

I think one way to optimize it is, like, uh, so I think one approach will be whatever did I already have. So let's say if I if I don't have anything, then I will have to fetch it anyway. So if we I I have a big list, I will, uh, do. So I will just look in, uh, let's say, Data for 10. I mean, if I go a long list, I will just designate it by 10. So every time user clicks on the next page or maybe it scrolls up, then we will show the next thing this next thing I'll introduce. So that's one way because then you you will not be rendering whole list in in one render. That is one thing. And the other thing is, like, you already have data some data that you want to update, like, frequently. So I will sort the old data first, and I will Behind the screen, uh, this new data and just update. Once the new data is That is another one. And definitely for the big list, we'll have some sort of paginations pagination other than uh

Uh, one way, like, uh, we have uh, the had its own file relations, but I think that is getting deprecated. Although I have never used it, I usually go with the files, but, yeah, uh, the whole prob validate or something. I don't remember. I think component dot props or prop validation, something like that. So you put the type there. So that way you can, uh, validate the type, but that that is getting uh, react

I think it depends. So, for example, if I have to Just, uh, here the component where I want to change the styling, let's say, More component way. By component way, I mean, we want to just put the top there in the based on the some condition, your top eye, the styles obtained. So rather than handling that myself, I can handle that in the styles I mean, CSS in there style, for example, if I use a style company. So I can handle that directly there in the style dot whatever element is there. Uh, so that place I will prefer to use, uh, style components or maybe I want to use a lot of add all the components or maybe compositions. Uh, but I usually prefer this CSS. Okay. Style seats. Yeah. So yeah. I mean, I generally don't preempt the style seat under yet. I'll definitely do with the style companies or maybe some CSS in the because with the style, you're, I mean, the readability is really bad, and the whole company becomes and also I don't I'd like to use

Uh, so profiler, I don't know. Never used. So but I think I think, basically, it gives you how many times your particular component of particular element is another component is rerendering. So you can see that and check if it is under Red rendering unnecessary for an application instance that should not redender the component, then, uh, that is a problem. So we can optimize