I love how project time always coincides with a momentous occasion!!! Off the high of all the inauguration revelry, I finally was able to focus on my Rails project. On top of that, I am also 20 weeks pregnant and it’s been a struggle being caught up with my coding, at least my energy level has been better than in my first trimester. Maybe my baby will be coding as soon as he’s out of the womb - LOL!
After the events of the past week though, I’m feeling an overall sense of hope!
I’m always guilty of taking too much time on planning, and over thinking my associations. Never thought something like associations would end up being one of the most complicated factors in building my Rails app. In hindsight, I really should have taken the time to update my diagram to get a better visualization of what I intended to do.
It took me a couple days to understand how to make sense my project, Eco Friend, which helps users source out eco-friendly alternatives through “Recommending a Brand!” and creating a “Review” for a new brand, be it looking for compostable trash bags or finding a compost bin near them.
As a refresher, our sub cohort lead, Eri, passed me this video to skim through and understand what a join model actually does. This helped tremendously. As soon as I got my associations set I made sure I started building right away since I had about a week and a day to work on my project as I typed this. I should have made it easy for myself and followed one of the examples in the project requirements, which were either a recipe manager or group task manager since the associations are more direct.
I found Cohort Lead, Jennifer Hansen’s videos to be very helpful, in particular this one: Rails MyBlog Project Build - Part 1 was extremely comprehensible and got me to set up almost flawlessly. I just had a minor glitch linking to my Github.
I got this error: <pathspec 'commit"' did not match any file(s) known to git, and Eri said that whichever branch I was on would be the one pushed to GitHub, by using git branch. If you’re on the main branch, which I’m usually on, you would have to put git push origin main.
SOLUTION: Key into your terminal
git remote origingit remote rm originremote add origin git@github.com:yani82/EcoFriend.gitgit remote originremote add origin git@github.com:yani82/EcoFriend.gitgit remote origingit push origin master- TO TEST AGAIN:
git branch
After which point, I was feeling good about the flow of building my project up until I used .build in my def new method, in my brand_controller. As I was typing this I was still stuck on it and moved to my create method, and commented the .build line out, then the form page didn’t show the whole create chunk in my views.
I eventually managed to resolve this, but unfortunately not being able to grasp my associations entirely kept causing me to switch around my code, making things feel more confusing than they already are. Thankfully, I was able to get the support from my cohort mates and I’m hoping to be able to wrap up my project soon. Currently, I’m still feeling like I’m drowning, so I’ll be sure to update this blog when I’ve completed my project. I wish I had more resources to share, but below are a few links that might help you along the way:
Another helpful resource to make sense of your associations, here via The Odin Project.
When setting up your Omniauth, “Google Authentication Strategy for Rails 5 Application” by Rachel Hawa, was extremely helpful.
If you’re unsure of your routes, instead of typing rake routes in your terminal, it may appear more cleaner if you typed this out in your browser: http://localhost:3000/rails/info/routes.
The best of luck on your Rails project comrades!