cribbed from http://pastebin.com/xgzeAmBn
Templates to remind you of the options and formatting for the different types of objects you might want to document using YARD.
| #!/usr/local/bin/ruby | |
| puts "Running application" | |
| class App | |
| def initialize(args) | |
| end | |
| def action(input) | |
| "input was #{input}" |
| #!/bin/bash | |
| # | |
| # Watch current directory (recursively) for file changes, and execute | |
| # a command when a file or directory is created, modified or deleted. | |
| # | |
| # Written by: Senko Rasic <[email protected]> | |
| # | |
| # Requires Linux, bash and inotifywait (from inotify-tools package). | |
| # | |
| # To avoid executing the command multiple times when a sequence of |
| Creating a Multi Page Form in Rails | |
| Creating a multi-step wizard-like form is pretty difficult in Rails. | |
| Especially when trying to apply REST and validations. There are many | |
| different approaches to this problem, and the right one depends largely | |
| on your application details. Here are four options, and then my final | |
| recommendation. Skip to that if you're in a hurry. | |
| 1. Create the model at the beginning on the first page of the form, and | |
| have each successive page update the model. Validations are tricky |