Fixed a bug with leading whitespaces in WKT #42
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
Not sure if this package gets updated too often anymore, but here's my 2 cents for fixing #36 which we've been running into recently.
Seems that the bug was caused by a missing
white()
call in the beginning ofcoords()
- confirmed that everything still seems to work in unit tests after the fix.Here's the list of changes:
white()
call to fix Parser does not parse wkt's with whitespace after first '(' #36browserify
todevDependencies
to makenpm install
work without global installationswellknown.js
- seems that the version previously used was somewhere between 9.0.0 and 11.2.0 (chose the latest)