Johan Alkstål johanalkstal

TLDR: a React component should either manage its own state, or expose a callback so that its parent can. But never both.

Sometimes our first impulse is for a component to entirely manage its own state. Consider this simple theater seating picker that has a letter for a row, and a number for a seat. Clicking the buttons to increment each value is hardly the height of user-interface design, but never mind - that's how it works:

/* @flow */
var React = require('react');

var Letter: React.ReactClass = React.createClass({
  getInitialState: function(): any {

This is now an actual repo:

https://github.com/cowboy/jquery-tiny-pubsub

	/*
	Copy this into the console of any web page that is interactive and doesn't
	do hard reloads. You will hear your DOM changes as different pitches of
	audio.

	I have found this interesting for debugging, but also fun to hear web pages
	render like UIs do in movies.
	*/

	const audioCtx = new (window.AudioContext \|\| window.webkitAudioContext)()

	{
	"version": "1.0",
	"components": [
	"Microsoft.VisualStudio.Component.CoreEditor",
	"Microsoft.VisualStudio.Workload.CoreEditor",
	"Microsoft.VisualStudio.Component.Roslyn.Compiler",
	"Microsoft.Component.MSBuild",
	"Microsoft.VisualStudio.Component.Static.Analysis.Tools",
	"Microsoft.VisualStudio.Component.Roslyn.LanguageServices",
	"Microsoft.VisualStudio.Component.PortableLibrary",

	[AttributeUsage(System.AttributeTargets.All, AllowMultiple = true, Inherited = true)]
	public class ಠ_ಠAttribute : Attribute
	{
	public ILog Log { get; set; }

	public ಠ_ಠAttribute()
	{
	Log.Info("This code is bad and you should feel bad");
	}
	}