jashkenas/backbone — pull request #3394 by akre54 (2014-11-21 14:35:10+00:00)
Title: Remove this.options from History

Is there ever a time where you'd want to make `Backbone.history`'s `this.options` part of its public interface? In my experience you're almost always going to set these properties by passing options to `history.start`.

The only case I can think of that you might need `this.options` is if you for some reason subclassed `Backbone.History`, but even then, in the vein of #2461, it'd make sense for these to be properties of the instance, not options. (Surprisingly, this change doesn't even break any tests.)

As an aside, Backbone History is an odd case because although it's almost required to use history as a singleton (you can't have two started Histories on the same page), we've exposed the constructor function for creating new instances like all the other classes. It'd seem to me that the singleton instance should just be a plain object; there should be no need to expose the constructor.