justin talbott waymondo

1. Gemfile

gem 'browserify-rails', '1.5.0' # until fix: https://github.com/browserify-rails/browserify-rails/issues/101
gem 'react-rails'

Browserify-rails allows to use browserify within assets pipeline. React-rails is here only to allow to use #react_component (and thus, prerendering).

Note that jquery-rails can be removed from Gemfile, the npm version of jquery and jquery-ujs will be used instead.

brew install gnupg, pinentry-mac (this includes gpg-agent and pinentry)
Generate a key: $ gpg --gen-key
Take the defaults. Whatevs
Tell gpg-agent to use pinentry-mac:
```
$ vim ~/.gnupg/gpg-agent.conf 
```

Testing a Generator in a Rails Engine

Testing a generator in a Rails engine can result in unwanted modifications of files in the test/dummy directory.

# lib/generators/my_engine/install_generator.rb
module MyEngine
  module Generators
    class InstallGenerator < Rails::Generators::Base
      source_root File.expand_path("templates", __dir__)

	/* bling.js */
	window.$ = document.querySelector.bind(document);
	window.$$ = document.querySelectorAll.bind(document);
	Node.prototype.on = window.on = function(name, fn) { this.addEventListener(name, fn); };
	NodeList.prototype.__proto__ = Array.prototype;
	NodeList.prototype.on = function(name, fn) { this.forEach((elem) => elem.on(name, fn)); };

	# The following comments fill some of the gaps in Solargraph's understanding of
	# Rails apps. Since they're all in YARD, they get mapped in Solargraph but
	# ignored at runtime.
	#
	# You can put this file anywhere in the project, as long as it gets included in
	# the workspace maps. It's recommended that you keep it in a standalone file
	# instead of pasting it into an existing one.
	#
	# @!parse
	# class ActionController::Base