| <%# app/views/layouts/application.html.erb %> | |
| ... | |
| <%= javascript_include_tag "locales/#{I18n.locale}", nonce: true %> |
| # This should be triggered through a cron job at 6:15 PM on week days. | |
| # Example cron: 15 18 * * 1,2,3,4,5 cd ~/code/jury_duty && ~/.rbenv/shims/ruby call.rb >> ~/code/jury_duty/call-log.txt 2>&1 | |
| # It uses Twilio to make a call based on TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN, and TWILIO_PHONE. | |
| # It calls the JURY_PHONE, transcribes it, looks for JURER_NUMBER and texts the result to PERSONAL_PHONE. | |
| require "rubygems" | |
| require "bundler/setup" | |
| Bundler.require(:default) | |
| Dotenv.load |
| class CreateNodes < ActiveRecord::Migration[6.0] | |
| def change | |
| create_table :nodes do |t| | |
| end | |
| create_table :node_edges do |t| | |
| t.integer :parent_id, null: false | |
| t.integer :child_id, null: false | |
| end | |
| # This sets up both a memory store and file system store for Shrine file uploads. | |
| # We use the memory store by default but in cases where you want to test actual | |
| # file uploads you can enable it with `file_upload: true` on a per example basis | |
| require "shrine/storage/memory" | |
| require "shrine/storage/file_system" | |
| # We use a delegator to swap out the storage dynamically | |
| # since the storage hash is duplicated for each uploader | |
| class Shrine::Storage::Dynamic < SimpleDelegator | |
| def initialize(initial, storages) |
| class EpisodeSearch | |
| attr_reader :ability, :options | |
| delegate :sanitize, to: Episode | |
| def initialize(ability, options = {}) | |
| @ability = ability | |
| @options = options.dup | |
| end | |
| def tag |
| cd ~/code/rails | |
| railties/bin/rails new ~/code/hello --edge | |
| cd ~/code/hello | |
| echo "gem 'puma'" >> Gemfile | |
| bundle | |
| rails g controller hello index | |
| # fill controller | |
| puma | |
| # separate tab | |
| curl localhost:9292/hello/index |
I took the ideas presented here and built a gem called Mustard. Check it out!
There are several expectation/assertion interfaces available for writing tests/specs. Here are some issues I have with them.
assert_equals feels backwardsassert_equal (that too)
In researching topics for RailsCasts I often read code in Rails and other gems. This is a great exercise to do. Not only will you pick up some coding tips, but it can help you better understand what makes code readable.
A common practice to organize code in gems is to divide it into modules. When this is done extensively I find it becomes very difficult to read. Before I explain further, a quick detour on instance_eval.
You can find instance_eval used in many DSLs: from routes to state machines. Here's an example from Thinking Sphinx.
class Article < ActiveRecord::Base
| class AssetHeaders | |
| def initialize(app) | |
| @app = app | |
| end | |
| def call(env) | |
| request = Rack::Request.new(env) | |
| response = @app.call(env) | |
| if request.path =~ /^\/assets\// | |
| # there maybe a better way to add headers |
| class TasksController < ApplicationController | |
| def update | |
| tracker = TaskTracker.new(@task) | |
| if @task.update_attributes(params[:task]) | |
| TaskPusher.new(tracker, socket_id).push_changes | |
| TaskMailSender.new(tracker, current_user).deliver_email | |
| # success response | |
| else | |
| # failure respond | |
| end |