Not sure if this helps, but here I have a tutorial that actually covers an entire CRUD app using FastAPI as a backend: ruclips.net/video/iLt00bqp6is/видео.html
You would have to create a new endpoint like "@app.delete("/remove_book")" and then write the logic in that function to remove the book at that index/key.
Try AWS Lambda: ruclips.net/video/RGIM4JfsSk0/видео.html The free usage limit is like 2M requests or something, so it's pretty much free until you start to have lots of users.
Why are you stick to those RPC style endpoint naming like "list-books", "add-book" etc? IMHO in REST world, your "list-books" will become "GET /books", "add-books" will become "POST /books" etc. The plural-vs-singular REST API entities naming is controversial and not so critical as sticking to RCP-style endpoints naming of REST APIs.
Hmm interesting, I haven't really seen many examples like "GET /books" as opposed to an explicit endpoint name, so I never even thought about it. I think one explanation is maybe you want multiple methods for the resource. E.g. "get-book" and "describe-book" (more verbose).
I think this is the best possible introduction for FastAPI! Kudos!
Thank you!
Really solid explanations without getting stuck. Your channel will blow up when the RUclips algorithm is on your side
Thanks! Glad you found it helpful!
Did the tutorial today and had a lot of fun!
Awesome, glad to hear that!
You're honestly a gem, I needed this!
Hope it helped!
Thank you for this video! Your channel is underrated.
Thank, I appreciate that!
Another great video. Thank you. Please keep them coming.
Thanks for the well explained tutorial, may i ask what the tool for command autosuggestion on the bash??
I used an autocomplete plugin for zsh there. More info in this video: ruclips.net/video/UvY5aFHNoEw/видео.html
Great Video. excellent pace. keep it up.
Thank you for this beautiful project , you have an example on put?
Not sure if this helps, but here I have a tutorial that actually covers an entire CRUD app using FastAPI as a backend: ruclips.net/video/iLt00bqp6is/видео.html
Great and well explained tutorial. Thank you!
You're welcome! I hope it's useful.
@pixegrami, how would I delete a book? I'm having trouble doing that. Thanks
You would have to create a new endpoint like "@app.delete("/remove_book")" and then write the logic in that function to remove the book at that index/key.
@@pixegami thanks for the response, I will try again and see if I can get it to work. Thank you.
Hi, I am having trouble running from the part when we introduced JSON file. I don't understand the problem.
Bro literally wonderful tutorial 🔥🔥.
Need more videos plz
Thanks! More to come!
Amazing tutorial! Also, may i know your vscode theme? 🙂
This is what I’ve been using: Monokai Pro monokai.pro/
this is great
Thank you so much 🙂❤
Can you make video about how to host api for free
Try AWS Lambda: ruclips.net/video/RGIM4JfsSk0/видео.html
The free usage limit is like 2M requests or something, so it's pretty much free until you start to have lots of users.
Why are you stick to those RPC style endpoint naming like "list-books", "add-book" etc? IMHO in REST world, your "list-books" will become "GET /books", "add-books" will become "POST /books" etc. The plural-vs-singular REST API entities naming is controversial and not so critical as sticking to RCP-style endpoints naming of REST APIs.
Hmm interesting, I haven't really seen many examples like "GET /books" as opposed to an explicit endpoint name, so I never even thought about it.
I think one explanation is maybe you want multiple methods for the resource. E.g. "get-book" and "describe-book" (more verbose).