Commit Graph

13 Commits

Author SHA1 Message Date
Antoine Pultier
63e22f0ed0 Manage empty L.LatLngBounds objects 2014-02-27 19:03:00 +02:00
Vladimir Agafonkin
91c039b7aa jshinting and major clean up of specs code, ref #2151 2013-11-07 23:54:33 +02:00
Seb Emonet
16f9c9a302 Accept simple objects in L.latLngBounds(). Fixes #1915. 2013-09-13 00:22:19 +02:00
Andrii Korzh
d1aa0f3b7e Update LatLngBoundsSpec.js 2013-05-18 13:27:45 +03:00
Tom MacWright
a2f7d7e834 Use mocha 2013-04-03 14:50:09 -07:00
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
5e05068478 complete LatLng and LatLngBounds tests, #1347 2013-02-05 15:21:40 +02:00
Yohan Boniface
4f59140253 Eat our own food 2013-01-28 01:09:26 +01:00
Yohan Boniface
4b5746ffbc Use getWest/South/East/North instead of getLeft/Bottom/Right/Top 2013-01-28 01:04:09 +01:00
Yohan Boniface
69b925b057 Add LatLngBounds.getLeft/getBottom/getRight/getTop 2013-01-27 12:12:02 +01:00
John Firebaugh
2cca6586dc Test the right class 2012-10-11 08:54:04 -07:00
Dominik Moritz
f8d6e7052e Implemented isValid() function for Bounds and LatLngBounds. Fixes issue #966. Added specification. 2012-09-11 12:43:16 +01:00
mourner
2b8d9eed1d LatLngBounds, moved MapSpec 2010-09-21 11:46:31 +03:00