Add Request Action with Redux Thunk
Guide Tasks
  • Read Tutorial
  • Watch Guide Video
Video locked
This video is viewable to users with a Bottega Bootcamp license

[00:00:01] Hi welcome back to the report that just got set up received support request function ality your erudition or interaction. So what's going on coronets 3 name names to say of support save news support request. That is all okay. Now we want to push to support requests from all of this. All right. Want to pass and embody the title and that's about it. For now let's see what the designer wants us to submit an image as well. We'll do that later on. Wow. Yeah. So for now it's just you. Is this a promise of save this party was tired of somebody with the closure. Let's copy this function title. Let's head over into our actions. So Sanjay us under actions and let's go ahead and read this function so we have a safe newsletter save news. So we're looking to kind of copy this functionality to solicit copy disinheriting. And I'd put the Sejdiu supporter was there so I can remember the title and pasted save new newsletter. I'm going to take the title save news support request and replace it right here. Case We have sent new support request. Title body in a callback right now. Here we just need to change the newsletter to say support request and we should be glad we are passing in the same day that pretty similar around let's just cut this and put it at the bottom here. Let's save it and save our support request and file. [00:01:48][106.8]
[00:01:49] Let's go to our browser and see if this is operational so we shouldn't have to go back since the new just a new item so we're just posting so we should just do what we need to do here. Once given a title it's called new request. This isn't working. Come fix your right know what's in the body and then hit save and we end saying. And it's not nothing's appearing okay. And the reason nothing is appearing is simply because we're trying to fill through these hard times right. And we gave it no time in yet any request here. So it's kind of lost our data. If we go to our post Bam here and we just get ARDE just a support request and I hit send on get we're going to get back. We're going to get it back but it has no title so that's a problem. But you can just ignore this. This object. I'm going to edit it real quick but you don't want to do this on the site at all. Okay so I'm a to support Quast slash slash while I want it. I'll just leave it. It's lost in a war. Get rid of that. I'll get rid of that. Another day. But yeah basically we need to pass in the status with it. So basically the status or I could fix that on the backend and just make it automatic. We should be appending a pending piece of data because anything we do here. We need it to automatically be pending. So what I'm going to do is I'm going to save it and I'm going to change honester this code. You're not going to write anything here you're just watching me right Kotake this. [00:03:53][123.9]
[00:03:54] You don't need to do this and if you hit on that's what you did because I just told you do and I did and I know it's going to show up pending because I'm going to make this change to the server that makes it so whenever you add it and I don't it's going to automatically status is automatically going to be automatically going to the penny machine. You're going to see it in pending so I'm going to change the no quake right in front of you. So status and having it make it I'm getting fetched from the ad but I'm just going to settle the painting because obviously it needs to be pending review requests pending so I'm going to do pending and see that I'm going to push the Roku. So that's where I'm typing off the screen. And you are going to do as you're just watching again. So get thinks the stoutness all right and that's fixed for me. It's already fixed for you because I've obviously already pushed this vote. You're watching it. But yeah. So I said fix us we can show you that it works when I hear it. Now you'll notice that enough to refresh the page. And this just so you kind of understand our backgrounds where you have to refresh page or anything after adding an item because it's on the back in your head that you are on it's going to be it's going to be whatever is on. So it's not about push. OK finally deployed to her OK now I can it give it a new title. Lots of new property requests please come fix my stuff. All right. [00:05:58][124.1]
[00:05:58] Body contact from some safe and we get a new item in here right here. Really awesome stuff. So we just implemented our request functionality really quick. Let's just go ahead and commit our cards get status get out get comment and I'm going to say implemented through West functionality for crafty requests feature. Okay so that's all done. The next thing we need to implement is the ability to change the status of a request need a button on here. What we see in our design that will allow us to move it to in progress and complete. So users will have this functionality which is why you can't see the button here but admins will have the ability to say okay this needs to be this needs to be in progress. This is now complete and there is for the user is simply just to view the status of their requests. So like OK submit your requests and admin user to carry it in progress right. So the end user is going to display in progress but that's all permissions. We'll get on to that actually after we get done with the functionality of the changing status request. So let's go ahead and look at the admin dashboard requests and you'll notice there's a button on each of these and when you click it it sends it while it sends it over to progress when you click it on in progress now it doesn't have one in here but I can very. We assume that it's going to be complete. That's the next stage you want to complete your progress item. There's no actions here on the design. [00:08:02][124.2]
[00:08:03] Now if I were working with a client and they provided me a design I wouldn't just go implement this and would immediately ask them what they wanted me to do because you don't want to go into a feature and then spend some time on mine even if it's like an hour you don't want to spend time on something and then bring them this feature and you have the client or he or she and have them say we don't want this piece functionality. So you want to always go check with your client and see that's what they want. Never just assume but since this is the design and there is no client that's got to be the next option. So we need a button and pending so we need it to go in progress in progress to go to complete. We'll talk more about this in the next guy but I want to end this guide since it's going off to go on too long and it's going sidetracked from the actual content of this guy. So hop into this content and the next gets one single status. And we already do that. So catching the next guy. [00:08:03][0.0]
[478.9]