Make sure you like the video and subscribe if you liked the content! It helps me continue producing content like this. Also, feel free to leave your suggestions about what other topics you'd like me to cover in future tutorials!
Thanks for your question! The Python docs recommend using uppercase because enumerations represent static values, and by convention generally we represent static values with all uppercase letters. In their opinion, it also helps to remind people that they need to call the .value attribute to get the actual value. The reason why I chose lowercases in this project is because the lowercase represents the actual shape of the value and so I think it makes it easier to relate it to the values in the OpenAPI spec. I also find all uppercases distracting, but that's just personal preference. When in doubt, though, follow the docs and/or stick to the conventions in the project you're working on.
Thanks for the nice feedback! I'll be definitely working on deployments in the coming videos, including Docker, Kubernetes, AWS, and simple options like Heroku as well!
Thank you for your question! In a real-world app we'd use a database, so this was just a choice to keep it super simple. You could just as well index by ID in a dictionary, it'd make access a lot faster 🚀!
Thank you
I'm really pleasantly surprised by the pace at which you're explaining things. I think the pace is just perfect not too slow, nor not too fast.
Really glad to hear that
Akbermet! Thank you for your kind feedback!
Super helpful José! Thanks very much!
Thank you for the nice feedback Steve!
Quite interesting. Keep them coming.
Thank you!
Make sure you like the video and subscribe if you liked the content! It helps me continue producing content like this. Also, feel free to leave your suggestions about what other topics you'd like me to cover in future tutorials!
Hello, nice tutorial! I have a question. Why you writing enum candidates, with lowercase when python docs recommends uppercase?
Thanks for your question! The Python docs recommend using uppercase because enumerations represent static values, and by convention generally we represent static values with all uppercase letters. In their opinion, it also helps to remind people that they need to call the .value attribute to get the actual value.
The reason why I chose lowercases in this project is because the lowercase represents the actual shape of the value and so I think it makes it easier to relate it to the values in the OpenAPI spec. I also find all uppercases distracting, but that's just personal preference.
When in doubt, though, follow the docs and/or stick to the conventions in the project you're working on.
wow thanks for the good video
! If you have a chance, I would appreciate it if you could make a video for fastapi deployment (using docker or etc)
Thanks for the nice feedback! I'll be definitely working on deployments in the coming videos, including Docker, Kubernetes, AWS, and simple options like Heroku as well!
One question.... why did you declare TODO as a list? why not a dict? if you have 500000 tasks and using a for loop to find a specific id... :(
Thank you for your question! In a real-world app we'd use a database, so this was just a choice to keep it super simple. You could just as well index by ID in a dictionary, it'd make access a lot faster 🚀!