| body { | |
| height: 2000px; | |
| } | |
| .big { | |
| font-size: 100px; | |
| } | |
| a { | |
| font-size: 12px; |
| # You need to have the HTTParty gem installed to run this | |
| # https://github.com/jnunemaker/httparty | |
| require 'httparty' | |
| response = HTTParty.get 'http://letsrevolutionizetesting.com/challenge.json' | |
| while response | |
| puts response | |
| follow_link = response['follow'].gsub('?', '.json?') |
git-sh loads your bash config from ~/.bashrc not ~/.bash_profile
So one way to fix this (this is how my machine is set up) is to copy your ~/.bash_profile to ~/.bashrc and then change ~/.bash_profile to just have this line:
test -f ~/.bashrc && source ~/.bashrc
The purpose of this document is to go over a couple different solutions for the AR Todos challenge from phase 1. First, I'm going to present a solution where most of the code is done in a single file. Then I'm going to present a solution using MVC and hopefully you'll be able to see the benefits of taking the time to separate your concerns.
Many beginner programmers would probably approach the AR Todos challenge in a manner somewhat like this example if they were not given specific instructions on how to implement the solution. This solution is easier to write because you can just tackle each task systematically without thinking about new classes, how to organize separate files, etc.
What if you made this program for your job and another person needed to add more functionality or fix a bug? Do you think it would be easy for them to understand what you did? They could probably figure it out, but it wouldn't be as easy as it could be. It's important to make your program as clea
This is an example MVC solution of the ActiveRecord TODOs: Part 1 challenge. The purpose of this document is to walk you through my thought process in creating this solution.
As always, the first thing I did was break this down into smaller problems. I decided to setup the database and then start with the view because I wanted to make an MVP as quickly as possible. Here's what I started out with:
require_relative 'config/application'
def display_menu
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="utf-8" /> | |
| <title>Blank HTML 5 Template</title> | |
| </head> | |
| <body> | |
| </body> | |
| </html> |
| #myMap { | |
| width: 800px; | |
| height: 500px; | |
| } |
| function List(listType) { | |
| this.items = []; | |
| this.total = 0; | |
| this.listType = listType; | |
| this.init = function() { | |
| if (this.listType === 'store') { | |
| this.makeItemsDraggable(); | |
| this.populateItems(); | |
| } else { |
In a large application, running all the tests at once using rake spec can make it difficult to check the output of the test you're working on. Especially if you have many failing or pending tests. Run a single test by running rspec:
rspec spec/models/account.rb
You can be even more specific and run a specific example from a test file. For example, given the following tests:
11: describe "#deposit!" do
When using Rails 3.0 and later we already get jquery-rails for free. Look in the gemfile and you'll see:
gem "jquery-rails"You can view the full documentation here: source: https://github.com/indirect/jquery-rails
If you take a look in APP_DIR/app/assets/javascripts/application.js, you'll notice the following lines of code: