f677f9c6d2
* Feat(Bounds): add getTopLeft & getBottomRight methods as suggested in #5475, for consistency with `LatLngBounds` methods which already provide methods for the 4 possible corners. Also include the docstrings. * Docs(Bounds): add comments to identify corners in BoundsSpec. * Test(Bounds): add tests for existing corner methods namely getBottomLeft and getTopRight. Checked that expecting different values make the tests fail. * Test(Bounds): add spec for 2 new corner methods namely getTopLeft and getBottomRight. Closes #5475 together with previous PR #5487. * Refactor(Bounds): return this.min(max) instead of new Point as TopLeft corner is tha same as this.min (BottomRight same as this.max). * Docs(Bounds): add links to this.min(max) to make it clearer that these methods are just shorthands to already available properties. Furthermore, it implies that they output those properties directly, making a clue for the app developer that if he/she wants to modify them, they should be cloned before doing so in order to prevent unintentional behaviour. |
||
|---|---|---|
| .. | ||
| BoundsSpec.js | ||
| LineUtilSpec.js | ||
| PointSpec.js | ||
| PolyUtilSpec.js | ||
| TransformationSpec.js | ||