Matt Huggins mhuggins

Add the utf8_sanitizer.rb to your Rails 3.2 project in app/middleware. Instead of removing the invalid request characters and continuing the request (as some gems do) it returns a 400 error.

Add the following line to your config/application.rb:

config.middleware.use 'Utf8Sanitizer'

If you only need it in production add to config/environments/production.rb. This can be without quotes:

config.middleware.use Utf8Sanitizer

Geeks Who Drink: Motherbrain Rounds and Questions Schema

Currently there are several changes to Motherbrain needed to accomodate the mobile and Quizmaster applications.

Round Types

During the course of a quiz, it's necessary for the mobile app and Quizmaster dashboard to be able to determine the type of Round being played.

These are the following round types:

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't

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.

Cross-origin web worker scripts

If you're like me and wanted to serve your main app script from a CDN and still load a web worker, you may have encountered the following error:

Uncaught DOMException: Failed to construct 'Worker': Script at 'http://cdn.example.com/worker.js' cannot be accessed from origin 'http://example.com'

You can get around this fairly simply with importScripts by making the script you instantiate your worker with load the actual worker script from the CDN.

	# # Frontend Build Process

	path = require('path')
	gulp = require('gulp')
	gutil = require('gulp-util')
	plumber = require('gulp-plumber')

	webpack = require("webpack")

	# ## CONSTS

	module BatchJobStateful
	extend ActiveSupport::Concern

	included do
	field :current_batch_id, type: String
	field :last_batch_total, type: Integer
	field :last_batch_failures, type: Integer
	field :last_batch_created_at, type: Time
	field :last_batch_completed_at, type: Time
	end

	// in preload scripts, we have access to node.js and electron APIs
	// the remote web app will not have access, so this is safe
	const { ipcRenderer: ipc, remote } = require('electron');

	init();

	function init() {
	// Expose a bridging API to by setting an global on `window`.
	// We'll add methods to it here first, and when the remote web app loads,
	// it'll add some additional methods as well.

	version: '3'
	services:
	neon-wallet-db:
	container_name: "neon-wallet-db"
	image: slipoh/neon-wallet-db:latest
	environment:
	- MONGOURL=mongodb:27017
	- MONGOPASS=neo
	- MONGOUSER=gas
	- MONGOAPP=test

	{
	"presets": ["es2015"],
	"plugins": ["transform-async-to-generator"]
	}