UI Updates for HTTP Verbs: Building a Postman Clone Course
HTML-код
- Опубликовано: 26 сен 2024
- In this lesson, we are going to update our user interface to allow for other types of commands. Specifically, we are going to add the ability for a user to call a POST command to our API. This will include the ability to send data in the body of our command.
Now this is lesson number 6 in our complete course on building a Postman clone. This course has been designed to be beginner-friendly and an example of what you might put in a portfolio. Although don't just directly put this course in your portfolio. Your portfolio needs to be uniquely yours, not just a copy of someone else's work.
Full Training Courses: IAmTimCorey.com
I have used WinForms for years, but watching this series excited me. Thank you so much for this.
You are welcome.
This is definitely getting better. Thank you for your work
You are welcome.
this is just exelent
Thank you!
As always. Thanks 😊
You're welcome.
Great! I can´t wait for the next session😀! So far I implemented everything in a WinUI 3 App, also used DI and a HttpClientFactory...not sure if this is overkill for a small Desktop App.
Great! Sounds like you've done a great job.
Great 👍
Thanks!
Why is text in the results tab automatically selected after you have sent the GET request?
We changed which tab was selected, but didn't specify what was the focus. We will change that in the upcoming video (although, you could do it now if you want to try to figure it out before I show it off).
I love the series, but one thing bugs me: technically, both tabs show body - body of request and body of response. With your naming, it's not 100% clear if body refers to request or response. I'd say that based on context, it's >90% clear, but still...
The actual Postman uses Body and Results. I went with Body and Response since I'm using the Response window for more than just results. Naming is tough. What would you name the tab (realizing that one word is ideal)?
@@IAmTimCorey Postman window has top part for request and bottom for response with subsections for elements of each with Body being 4th tab for Request and 1st for Response. I'd call tabs Request and Response, but I would also add a small label to identify the whole section as Body. I realize I'm nitpicking, but when I'm working with something with established naming I try not to mess with it, so people know what to expect.
I have a question. For the post command, are you going to do it where it can automatically prepopulate the json so you just change the values. Because I would think that if a person just manually types in the json, that is not user friendly. Even when typing c# code, you have lots of intellisense. This really needs at least repopulating the json so you just change the values as needed. Or even better yet, a ui with text boxes to make it as user friendly as possible.
I'm not sure what you mean by "automatically prepopulates the json". How would the UI know what the JSON structure should look like? Also, not every call will be JSON data.
Thanks again, Tim
You are welcome.