Before #53 the implementation already supported both null and undefined precisions, but this was never tested properly, only slightly with a lazy assert.equal( …, null ) that accepts undefined as null. #53 broke this feature, but not the test, because it was never calling equals with an undefined precision.
Before #53 the implementation already supported both null and undefined precisions, but this was never tested properly, only slightly with a lazy
assert.equal( …, null )
that acceptsundefined
asnull
. #53 broke this feature, but not the test, because it was never callingequals
with an undefined precision.The backend also supports precision null, see https://github.com/DataValues/Geo/blob/master/src/Values/GlobeCoordinateValue.php.