You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
parse-coordinates already works directly as a validator because a coordinate array casts to a "true" boolean value, while the null returned on a parsing value casts to a "false" boolean value.
The value of adding it to or validator.js would be that it is more convenient to find.
@markstos thanks for replying. Yes, that was the intention; to use it as an internal dependency within validator.js and make it available for convenience
Support for isLatLong:
Libraries that currently validate and return lat,long coordinate pairs:
@markstos has forked to-coordinates [that was lacking stricter parsing which he has raised in the issue here: Wish: stricter parsing of lat/long coordinates pairs #2] to create a stricter parsing of lat/long pairs in a wonderful library called parse-coordinates
We could use this to support -
isLatLong('12.0122,-77.00')
within this library.If I were to put something together for a PR, do you support reuse of parse-coordinates as a dependency here or write the entire code here?
The text was updated successfully, but these errors were encountered: