Skip to content

Instantly share code, notes, and snippets.

undefined method `status' for nil:NilClass

Élisson Michael elissonmichael

undefined method `status' for nil:NilClass
View GitHub Profile

Commit Message Guidelines

Short (72 chars or less) summary

More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).

Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages
elissonmichael /
Last active Dec 13, 2019 — forked from rastasheep/
MiniTest quick reference


use must for positive expectations and wont for negative expectations.

  • must_be | list.size.must_be :zero?
  • must_be_close_to | subject.size.must_be_close_to 1,1
  • must_be_empty | list.must_be_empty
  • must_be_instance_of | list.must_be_instance_of Array
  • must_be_kind_of | list.must_be_kind_of Enumerable
elissonmichael / inflections.rb
Created Aug 6, 2018 — forked from mateusg/inflections.rb
pt-BR inflections file for Ruby on Rails applications
View inflections.rb
# encoding: utf-8
# Be sure to restart your server when you modify this file.
# Add new inflection rules using the following format
# (all these examples are active by default):
# ActiveSupport::Inflector.inflections do |inflect|
# inflect.plural /^(ox)$/i, '\1en'
# inflect.singular /^(ox)en/i, '\1'
# inflect.irregular 'person', 'people'
# inflect.uncountable %w( fish sheep )
elissonmichael / rails http status codes
Created Oct 22, 2019 — forked from mlanett/rails http status codes
HTTP status code symbols for Rails
View rails http status codes
HTTP status code symbols for Rails
Thanks to Cody Fauser for this list of HTTP responce codes and their Ruby on Rails symbol mappings.
Status Code Symbol
1xx Informational
100 :continue
101 :switching_protocols
102 :processing
elissonmichael /
Created May 30, 2018 — forked from speric/
Notes From "Practical Object-Oriented Design In Ruby" by Sandi Metz

Chapter 1 - Object Oriented Design

The purpose of design is to allow you to do design later, and it's primary goal is to reduce the cost of change.

SOLID Design:

  • Single Responsibility Principle: a class should have only a single responsibility
  • Open-Closed Principle: Software entities should be open for extension, but closed for modification (inherit instead of modifying existing classes).
  • Liskov Substitution: Objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program.
  • Interface Segregation: Many client-specific interfaces are better than one general-purpose interface.
elissonmichael / pilha_dinamica.c
Last active Jun 17, 2019
Estrutura de Dados - Pilha Estática vs Dinâmica & Palíndromo
View pilha_dinamica.c
#include <stdio.h>
#include <stdlib.h>
typedef struct {
int valor;
struct No *proximo;
} No;
typedef struct {
No *topo;
elissonmichael / test_mail_purge.rb
Created Jun 3, 2019 — forked from adamsanderson/test_mail_purge.rb
An example of using MiniTest::Mock
View test_mail_purge.rb
require 'minitest/mock'
require 'minitest/unit'
require 'date'
class TestMailPurge < MiniTest::Unit::TestCase
class MailPurge
def initialize(imap)
@imap = imap
View capybara cheat sheet
=Clicking links and buttons=
click_link('Link Text')
click('Link Text') # Click either a link or a button
click('Button Value')
elissonmichael / brute_force.rb
Last active Apr 14, 2019
Algoritmo para Resolver uma Charada por Força Bruta em Ruby
View brute_force.rb
(100..999).each do |x|
(100..999).each do |y|
(100..999).each do |z|
soma = x + y + z
condicao1 = soma.digits.size == 3
condicao2 = soma.digits.uniq.size == 1
n = soma.digits.uniq.first
condicao3 = n == x.digits.first && n == y.digits.first && n == z.digits.first
condicao4 = x.digits.last == y.digits.last && y.digits.last == z.digits.last
condicao5 = x.digits[1] == y.digits[1] && y.digits[1] == z.digits[1]
View atom-ruby-snippets.cson
'describe (String)':
'prefix': 'des'
'body': 'describe "${1:subject}" do\n $0\nend'
'describe (type)':
'prefix': 'dest'
'body': 'describe ${1:Type} do\n $0\nend'
'describe (type, string)':
'prefix': 'dests'
'body': 'describe ${1:Type}, "${2:description}" do\n $0\nend'