Fixing the Props Issue
Guide Tasks
  • Read Tutorial
  • Watch Guide Video
Video locked
This video is viewable to users with a Bottega Bootcamp license

[00:00:00] Hi there. Welcome back to the reactor building in this time we are going to be fixing this error that we got on the screen whenever we tried to sign him. He says this stuff props of signing a user is not a function. So basically it's not recognizing our next actions right. You're not recognizing now we are trying to hit one of these functions which is an end user. So super simple. Thanks I'm going to exit out of all of these files and I'm going to hop straight into the site Georgia. Yes. And I'm going to start here. So basically what's happening is we don't have access to our functions our actions because our outerwear and title are messing things up. So first thing I want to do to make this clear what's going on is I'm going to separate all these into all we of different redux for so many see a sign is equal to and then I'm going to take everything out of here and I'm not throw it in right here. Who's right here. Right now I'm going to cut out title. You can replace the sign right now that I'm going to say side is equal to title and then sign it. So what's happening here is we're saying OK at the border to our signing and signing. So basically this is no different than saying this. All right. So real quick if I can Nancy. This is what we want right. So I did it backwards. [00:01:35][95.1]
[00:01:36] We want to say we want to replace these two sons connected CNN and put it above board and then I'm going to sign him back in the next year. And then going to page we have what we saw. But if I had signed him. So we are still recognizing our function. So all we have to do is. And the reason it's not is because this is props right sending users super props because of Connec here and I hope that you were props again. So just think flow here we're passing and signing. We're going title Bring the child here but we're not declaring any props on the child. So we have to specify that this child has the props we have to say this not props reasons for that operator so we can apply them like we would like we did with that request. Do you remember how that works. So now child are signing Kampar and has access to its own props now. All right. Now that might be really confusing but try to think about it and trying to understand that we're basically just taking the side and props and we're reassigning you to sign it. OK. Now it's still not working because we are adding another layer. I have no further comment this hour and it's just a title. We did this all props so the child is receiving all its original props which includes the actions. Now if I go back to the browser signing works it says that request is being provided and credentials so we got that request from the server got network and the red sign it says that requests B.M.. [00:03:26][109.2]
[00:03:27] So the way we can fix this is by simply doing the same thing and I had a reporter coming in here and saying in brackets dot.com this stuff drops. OK. Now that we have that out it should be functional. Let's check it out in our browser and see what happened in dot com. Let's just say Hosford to sign in and we were able to sign it redirects us like we have set up when we first started the site and we should have a token over here if we ever archive. We were told again that should be in our local store cheer token and yeah we're all set up. We have the sign form complete. Now I'm going to now get back to 30 time or just my room and yeah that's all good to go. So since restyling. I mean there's something we could hear such as checking if the password and I mean I know that it might be needed say OK there's there's something wrong in these fields and that goes back to redux. But I want to get around to world once we get through all of. Some kind of treating this kind of like a you know modular approach so to speak. So the first thing we did is get out the majority of the functionality and get 80 percent of it and then now we're going through all the styles which will allow us to see the nice upgrade and Marjorie the functionality is there and then we'll go back when we're done with all the styles and we will get in the rest of the functionality which includes permissions such as the user reusing and protected routes and obviously formed validation. So we'll get around to that when we get around to it. [00:05:23][116.0]
[00:05:23] But for now let's just keep going hard with the styles. We know that our app is working for the most part. Just a few buttons here. So let's go out and commit our code and let's say it's not as good I get it. I must just say the word fixed crops issue with agencies. OK now I'll see you the next guy where we will start we will start styling our newsletter component and components within her. So I'll see. [00:05:23][0.0]
[320.3]