| module ApplicationHelper | |
| def current_class?(test_path) | |
| return 'active' if request.path == test_path | |
| '' | |
| end | |
| end |
| module MyApp | |
| class Application < Rails::Application | |
| require Rails.root + 'lib/custom_public_exceptions' | |
| config.exceptions_app = CustomPublicExceptions.new Rails.public_path | |
| end | |
| end |
| # Support for Rspec / Capybara subdomain integration testing | |
| # Make sure this file is required by spec_helper.rb | |
| # (e.g. save as spec/support/subdomains.rb) | |
| def switch_to_subdomain(subdomain) | |
| # lvh.me always resolves to 127.0.0.1 | |
| hostname = subdomain ? "#{subdomain}.lvh.me" : "lvh.me" | |
| Capybara.app_host = "http://#{hostname}" | |
| end |
| $OutputEncoding = New-Object -typename System.Text.UTF8Encoding | |
| [Console]::OutputEncoding = New-Object -typename System.Text.UTF8Encoding |
It's pretty easy to do polymorphic associations in Rails: A Picture can belong to either a BlogPost or an Article. But what if you need the relationship the other way around? A Picture, a Text and a Video can belong to an Article, and that article can find all media by calling @article.media
This example shows how to create an ArticleElement join model that handles the polymorphic relationship. To add fields that are common to all polymorphic models, add fields to the join model.
By default, Rails applications build URLs based on the primary key -- the id column from the database. Imagine we have a Person model and associated controller. We have a person record for Bob Martin that has id number 6. The URL for his show page would be:
/people/6
But, for aesthetic or SEO purposes, we want Bob's name in the URL. The last segment, the 6 here, is called the "slug". Let's look at a few ways to implement better slugs.