Recent snippets posted on Snipplr.com https://snipplr.com/ Wed, 10 Jun 2026 13:32:56 +0000 https://snipplr.com/view/25493/requiring-javascript-and-css-in-rails-without-directly-injecting-code-into-the-head-element <p>I used to directly inject javascript and CSS into my HEAD elements just like you see in all of the tutorials online and in books. Recently I decided to try a different approach, and I feel this is more in keeping with the ruby and rails "declaration" syntax. It has the added benefit of promoting unobtrusive javascript coding and factoring out page-specific CSS into its own file.</p> Sun, 27 Dec 2009 00:35:18 UTC https://snipplr.com/view/25493/requiring-javascript-and-css-in-rails-without-directly-injecting-code-into-the-head-element https://snipplr.com/view/25492/requiring-javascript-and-css-in-rails-without-directly-injecting-code-into-the-head-element <p>I used to directly inject javascript and CSS into my HEAD elements just like you see in all of the tutorials online and in books. Recently I decided to try a different approach, and I feel this is more in keeping with the ruby and rails "declaration" syntax. It has the added benefit of promoting unobtrusive javascript coding and factoring out page-specific CSS into its own file.</p> Sun, 27 Dec 2009 00:35:17 UTC https://snipplr.com/view/25492/requiring-javascript-and-css-in-rails-without-directly-injecting-code-into-the-head-element https://snipplr.com/view/25399/monkeypatch-for-easier-to-read-migrations <p>I never can remember the exact name of the exception to call in self.down for a migration that cannot be undone. So I decided to come up with something easier to remember. This feels more "ruby-ish" and "rails-ish" to me, and so far it works just fine. It also displays a message that is easier to pick out amongst all the other migration output on the screen so you can see at a glance that it failed.</p> Thu, 24 Dec 2009 22:37:41 UTC https://snipplr.com/view/25399/monkeypatch-for-easier-to-read-migrations