isValidCoordinate

[M-Scott-Lassiter]

Description

This matcher follows the same rules as isValid2DCoordinate and isValid3DCoordinate. This particular matcher takes an argument of either a 2D or 3D coordinate and checks its validity.

It takes as an argument of an individual array value (i.e. not the entire coordinates property).

Valid GeoJSON Coordinate Examples

A two-element array of points:

{
   "type": "Feature",
   "geometry": {
       "type": "Point",
       "coordinates": [102.0, 0.5]
   },
   "properties": {
       "prop0": "value0"
   }
}

An array of coordinates:

{
   "type": "Feature",
   "geometry": {
       "type": "LineString",
       "coordinates": [
           [102.0, 0.0],
           [103.0, 1.0, -100],
           [104.0, 0.0, 0],
           [105.0, 1.0, 100]
       ]
   }
}

In each case, the matcher should only get passed the value of a single coordinate, not the object itself.

Example Matcher Usage

expect([22, -34.549]).isValidCoordinate()
expect([22, -34.549, 1000]).isValidCoordinate()

expect([322, -34.549, 0]).not.isValidCoordinate() // Longitude out of range
expect({coordinates: [22, -34.549, 22]}).not.isValidCoordinate() // Coordinates object instead of array

Repeat Tests Contained in Other Files

This matcher works with either 2D or 3D coordinates. Therefore, the passing and failing tests for isValid2DCoordinate and isValid3DCoordinate can also include tests for isValidCoordinate.

Unique Tests

• Incorrect number of array elements (because 2D and 3D have conflicting tests for the combined matcher)
  • [ ], [ 20 ], [20, 30, 0, 4], [20, 30, 0, 20, 30, 0, 20, 30, 0]
• Snapshot Testing

[M-Scott-Lassiter]

🎉 This issue has been resolved in version 1.0.0-beta.2 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[M-Scott-Lassiter]

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀