-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kld/master - final PR #50
base: kld/master
Are you sure you want to change the base?
Conversation
@@ -0,0 +1,3 @@ | |||
# Place all the behaviors and hooks related to the matching controller here. | |||
# All this logic will automatically be available in application.js. | |||
# You can use CoffeeScript in this file: http://coffeescript.org/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not required, but you could consider removing extraneous .coffee files that you are not using as a way to clean up your application directory.
Great work on this project @kdefliese ! It is clear that you understand key ruby concepts around CRUD actions and it is awesome that you are exploring new things with trying to implement single table inheritance. Some of my notes are small style-guide-type comments, which aren't critical but are good habits to build early on. Industry code reviewers will notice and appreciate the readability. Keep it up! |
After I set up individual models/controllers/views/tests, I decided to refactor and break everything. I used a tutorial on single table inheritance to set up a single model/controller/set of views for Medium. This went pretty well, but the paths got pretty complicated. I used some helper functions that were in the tutorial to construct paths, but I wasn't 100% sure how that was working/how to test everything, so it's a little bit wonky in places...
http://samurails.com/tutorial/single-table-inheritance-with-rails-4-part-1/ is the tutorial that I used.