Do not parse numeric values in Point coordinate setters #138
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@djlambert could you please take a look at this PR? :) |
|
@JanJakes would you please reopen this PR against the develop branch? We moving to a GitFlow work flow and the code for the next release is being staged there. I'll add some tests and we'll get 1.1.2 released. |
|
Reopened as #141. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
At the moment every value is parsed (even if it's already float) which means that parsing
0.00001fails because(string) 0.00001is1.0E-5and that fails in geo-parser (see creof/geo-parser#7).