Commit Graph

5 Commits

Author SHA1 Message Date
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
Vladimir Agafonkin
382ef5c0b2 spec cleanup 2012-07-05 12:54:40 +03:00
Andrey Rublev
263a5b9b5f Add method Polyline.closestLayerPoint
Also fix method L.LineUtil.simplify for empty geometry
2011-07-20 13:23:04 +07:00
Mourner
61d636cc4f remove noSpec failures (enable when needed during development) 2011-07-12 14:59:43 +03:00
mourner
42bcb9b3b3 DomUtil, DomEvent, namespace config improvements, some specs 2010-09-07 14:27:44 +03:00