Pierre de La Morinerie kemenaran

The Unofficial 37signals/DHH Rails Style Guide

About This Document

This style guide was generated by Claude Code through deep analysis of the Fizzy codebase - 37signals' open-source project management tool.

Why Fizzy matters: While 37signals has long advocated for "vanilla Rails" and opinionated software design, their production codebases (Basecamp, HEY, etc.) have historically been closed source. Fizzy changes that. For the first time, developers can study a real 37signals/DHH-style Rails application - not just blog posts and conference talks, but actual production code with all its patterns, trade-offs, and deliberate omissions.

How this was created: Claude Code analyzed the entire codebase - routes, controllers, models, concerns, views, JavaScript, CSS, tests, and configuration. The goal was to extract not just what patterns are used, but why - inferring philosophy from implementation choices.

	# A test controller that holds a request for the given time, then returns.
	# Useful for testing requests that time out in Capybara.
	#
	# Usage:
	# mock_posts_controller = HoldingController.new
	# PostsController.stubs(:new).returns(mock_posts_controller)
	# mock_posts_controller.holding_actions do
	# # do something that should time out
	# assert_text "The request timed out"
	# end

	# Match the JSON body of the request, ignoring some specified keys.
	#
	# Usage:
	# VCR.use_cassette(
	# 'my_request',
	# match_requests_on: [:host, :path, body_as_json_excluding(:timestamp)]
	# )
	#
	# See also: body_as_json
	def body_as_json_excluding(*keys)

	# By default, ActiveRecord logs SQL statements during tests – including when
	# creating fixtures.
	#
	# When a Rails app has many fixtures, those logs can clobber test logs with
	# a lot of logged SQL statements.
	#
	# We could disable ActiveRecord SQL logs entirely during tests, but having
	# SQL queries displayed during tests is useful. Instead this snippet disables
	# the ActiveRecord SQL logs just when loading fixtures.
	#

	#!/usr/bin/env ruby
	#
	# Given a source file, scan the unresolved data raw addresses,
	# and emit an SYM file with additional data labels for those addresses.
	#
	# This SYM-file can then be fed into mgbdis to generate a new disassembly
	# that includes the proper data blocks.
	#
	# For best results:
	# - Document symbols in the original source file the best you can.

	<?php

	/**
	* Plugin Name: ColibriWP Fix Options
	*
	* How to use:
	*
	* 1. Put this file inside the wp-content/plugins/ directory;
	* 2. In the Wordpress Dashboard, navigate to the Extensions page;
	* 3. Enable the "ColibriWP Fix Options" extension;

	validates_associated :champs, :champs_private
	# -> Rails displays: "Champs is invalid"

	validates_associated :champs, :champs_private, message: -> (object, _data) {
	(object.champs + object.champs_private)
	.reject(&:valid?)
	.flat_map do \|champ\|
	champ.errors.full_messages.map do \|message\|
	"#{champ.libelle} : #{message}"
	end

	#ifndef NS_DESIGNATED_INITIALIZER
	#if __has_attribute(objc_designated_initializer)
	#define NS_DESIGNATED_INITIALIZER __attribute((objc_designated_initializer))
	#else
	#define NS_DESIGNATED_INITIALIZER
	#endif
	#endif

	---
	:verbose: true
	:update_sources: true
	gem: --no-rdoc --no-ri
	:backtrace: false
	:bulk_threshold: 1000
	:benchmark: false