It was by so far best video on PERN stack !!!!, I wish I saw this video when I was creating my final project but nonetheless, you are a great teacher !
Just a heads up. If you downloaded the project or cloned it from the repo and you can't connect to the postgres DB, it might be because the version of the pg package that was used in this video doesn't work with versions of node that are >= 14. I'm using node v16 and was having issues with connecting. I uninstalled the version pg that was used here and reinstalled the latest version of pg. After that everything worked.
Thank you so much for all the tutorials you have posted. They are the best PERN tutorials I have been able to found. Would you be able to give us a more thorough project tutorial like this one but with more robust and real life like authentication and authorization (such as password validation) and more fully fledged out user interfaces? Something like a e-commerce site with shopping cart and check out so transaction can also be touched upon. That would be really cool.
Great video! Could it be possible for you to make a video showing how to implement a feature to let you see your todos as well as other users’? Maybe from users in your team, or friends list, to be able to share todos back and forth. Thank you!
Thank you, interesting video, many things are described in great detail. What are your plans for video tutorials? Maybe you plan to make a video cycle on the development of some major project?
Thanks, Alexandr, interesting question. I don't have much of a plan, I sometimes read the comment section and if I find a suggestion that sounds prevalent then I probably make a video on it.
beautifully done video. I guess this was the last installment, but if I may make (another) suggestion... Adding a few extra features every now and then to show how to extend a database design and introduce maybe a few more basic concepts would be awesome! Like, how do you decide which features would be added to the user (or todo) table, and which would be better if give their own table?
Howdy Compte, I don't plan to end this project anytime soon. I am planning to equip this with other technology. Probably not the answer you are looking for, but it comes down to how you want to design it. That is why the first step in any development would be database design because it gives you an idea of what entity is in your application and how you want them to interact with each other. Here is a nice video of 2 software developer planning a car registration company by designing the database from scratch => ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-ITSboWxJCAQ.html. It should give you insight into how they think before building the application.
Hey these sessions are really great. I learnt a lot of things in this. One more suggestion from my side in this application. Can you add pagination option for todos using react. ? Can you make a seperate video about that. And also if possible the mail things.
Thanks for making these amazing videos, Your videos are so much fun and I learn a lot from them. QUESTION, as you know that we have used useEffect and the components were re-rendered many times, if the application gets bigger, will these re-renders affect the performance of the app? and if yes then how can we use useRefs useCallbacks etc to keep the re-renders to the minimum? Thanks
It would be awesome if you expanded on this like so: - Anyone, logged in or not, can access anyone else's dashboard by their name (e.g. "/dashboard/henry") - You can only modify your own todos while you are authenticated at "/dashboard/" This would demonstrate how to transform this app into a public profile based website where users can control their own content
useEffect(() => { getProfile(); setTodosChange(false); }, [todosChange]); as we are doing setTodosChanges(false) inside useEffect. It causes useEffect to be called again due to which we are making two api request to fetch the todos
I wonder, wouldn't it be better to create all the todos under the user instead of making a new entry every time? like, now every time there is a new todo, there is the user id in it as well. doesn't this use a lot of storage over time? I wonder, can you just append the new todo to the first existing one and just change the todo id? Like this: user_id | todo1 | todo2 | [...] 1 | Clean | Cook | [...]
i got this error 401 (Unauthorized) same from the previous tutorial. i can see the landing page but in the console shows that error. i noticed i also cannot register account and the terminal shows false
