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.
| //////////////////////push_notifications.js/////////////////////// | |
| var apns = function(){ | |
| var pref = require('preferences').preferences; | |
| Titanium.Network.registerForPushNotifications({ | |
| types: [ | |
| Titanium.Network.NOTIFICATION_TYPE_BADGE, | |
| Titanium.Network.NOTIFICATION_TYPE_ALERT | |
| ], | |
| success:function(e) |
| module Log | |
| module Minimal | |
| [:fatal, :error, :warn, :info, :debug].each do |method| | |
| define_method "#{method}f" do |message| | |
| time = Time.now.iso8601 | |
| level = method.to_s.upcase | |
| caller = "%s#%s:%s" % [self.class, action_name, caller(1)[0].scan(/:(\d+):/)] | |
| logger.send(method, "%s [%s] %s %s" % [time, level, caller, message]) | |
| end |
a list of slides from nodeconf
you may want to take a look at the jsconf-gist too!
| # Forked to get it working with Rails 3 and RSpec 2 | |
| # | |
| # From http://github.com/jaymcgavren | |
| # | |
| # Save this as rcov.rake in lib/tasks and use rcov:all => | |
| # to get accurate spec/feature coverage data | |
| # | |
| # Use rcov:rspec or rcov:steak | |
| # to get non-aggregated coverage reports for rspec or steak separately |
| (defun anything-c-sources-git-project-for (pwd) | |
| (loop for elt in | |
| '(("Modified files (%s)" . "--modified") | |
| ("Untracked files (%s)" . "--others --exclude-standard") | |
| ("All controlled files in this project (%s)" . "")) | |
| collect | |
| `((name . ,(format (car elt) pwd)) | |
| (init . (lambda () | |
| (unless (and ,(string= (cdr elt) "") ;update candidate buffer every time except for that of all project files | |
| (anything-candidate-buffer)) |
| #compdef _rake rake | |
| _rake_does_task_list_need_generating () { | |
| if [[ ! -f .rake_tasks ]]; then return 0; | |
| else | |
| return $([[ Rakefile -nt .rake_tasks ]]) | |
| fi | |
| } | |
| _rake () { |
With Rails 3.0 released a few weeks ago I've migrated a few apps and I'm constantly finding useful new improvements. One such improvement is the ability to log anything in the same way that Rails internally logs ActiveRecord and ActionView. By default Rails 3 logs look slightly spiffier than those produced by Rails 2.3: (notice the second line has been cleaned up)
Started GET "/" for 127.0.0.1 at Mon Sep 06 01:07:11 -0400 2010
Processing by HomeController#index as HTML
User Load (0.2ms) SELECT `users`.* FROM `users` WHERE (`users`.`id` = 3) LIMIT 1
CACHE (0.0ms) SELECT `users`.* FROM `users` WHERE (`users`.`id` = 3) LIMIT 1
Rendered layouts/_nav.html.erb (363.4ms)
| =Navigating= | |
| visit('/projects') | |
| visit(post_comments_path(post)) | |
| =Clicking links and buttons= | |
| click_link('id-of-link') | |
| click_link('Link Text') | |
| click_button('Save') | |
| click('Link Text') # Click either a link or a button | |
| click('Button Value') |