bf4

Relevant Rails PRs

• rails/rails#16052
  • https://github.com/rails/rails/commit/9e42cf019f2417473e7dcbfcb885709fa2709f89
• https://github.com/rails/rails/commit/2c46d6db4feaf4284415f2fb6ceceb1bb535f278
• https://github.com/rails/rails/commit/39f2c3b3ea6fac371e79c284494e3d4cfdc1e929
• https://github.com/rails/rails/commit/bdc5141652770fd227455681cde1f9899f55b0b9
• https://github.com/rails/rails/commit/d26dd00854c783bcb1249168bb3f4adf9f99be6c

h/t to http://juanitofatas.com/2015/01/31/rails-5-active-record-or/ for some more useful links

staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

nubbel

protocol ArrayRepresentable {
    typealias ArrayType
    
    func toArray() -> ArrayType[]
}

extension Range : ArrayRepresentable {
    func toArray() -> T[] {
        return T[](self)
    }

stevenyap

This describes the workflow to use Heroku as a staging environment. It assumes you already have an existing heroku app in production.

# rename your git remote heroku to something else like production
git remote rename heroku production

# so now you will push as: git push production master

# create the staging app
heroku apps:create staging-appname

lancefisher

$.rails.allowAction = function(link) {
  if (!link.attr('data-confirm')) {
    return true;
  }
  $.rails.showConfirmDialog(link);
  return false;
};

$.rails.confirmed = function(link) {
  link.removeAttr('data-confirm');

dhh

# config/routes.rb
resources :documents do
  scope module: 'documents' do
    resources :versions do
      post :restore, on: :member
    end

    resource :lock
  end
end

dhh

class GroupersController < ApplicationController::Base
  def create
    @grouper = Grouper.new(leader: current_member)

    if @grouper.save
      confirm_grouper_via_emails(@grouper)
      enqueue_bar_assignment(@grouper)

      redirect_to home_path
    else

josevalim

# Elixir v1.0
defmodule Rules do
  defmacro __using__(_) do
    quote do
      import unquote(__MODULE__)
      @before_compile unquote(__MODULE__)
      @rules []
    end
  end

seyhunak

$.rails.allowAction = function(link) {
  if (!link.attr('data-confirm')) {
    return true;
  }
  $.rails.showConfirmDialog(link);
  return false;
};

$.rails.confirmed = function(link) {
  link.removeAttr('data-confirm');

kidpollo

Pundit has a helper method policy_scope that can be used in controllers and views that basicaly a class finder. It is equivalent to:

@posts = policy_scope(Post)
@posts = PostPolicy::Scope.new(current_user, Post).resolve

Using the helper is a nice approach because you dont have to remember what Scope class you need. This is all fine and well on a world where the app is single teanant or the auth logic to reslove scopes needs no other context but the user and the resource that is being requested.

In our world almost all requests are nested under a company context and require a current user to determine membership role to present certain data.