John Firebaugh 01332ebead Omit "should" in spec descriptions ... The rationale is this: the spec string describes the expected behavior unconditionally. The code examples, on the other hand, set up an expectation that is tested with the call to the expect method. The code examples can violate the expectation, but the spec string does not. The value of the spec string is as clearly as possible describing the behavior. Including “should” in that description adds no value. (From http://rubyspec.org/style_guide/)		2013-02-19 12:41:48 -08:00
..
vector	Omit "should" in spec descriptions	2013-02-19 12:41:48 -08:00
FeatureGroupSpec.js	Change _propagateEvent to be careful that it doesn't overwrite e.layer if it is already set. Allows markers to be in multiple FeatureGroups and have the events come through correctly. See the test for details.	2013-02-08 14:44:28 +13:00
TileLayerSpec.js	Omit "should" in spec descriptions	2013-02-19 12:41:48 -08:00