fix regex pattern for gps coordinates #5578
Merged
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
Too short Numbers like 1.23 were not recognised by the old logic. Instead you would have to write 1.230. The new pattern now also supports natural numbers like 1 and 2 as well as 1.1 and 2.2
|
did it result on crashes? |
YvesHenri
approved these changes
Sep 21, 2016
|
👍 |
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.
Short Description:
fixes limited input for gps-coordinates in json files in FollowPath worker.
Too short Numbers like 1.23 were not recognised by the old logic.
Instead you would have to write 1.230.
The new pattern now also supports natural numbers like 1 and 2 as well as 1.1 and 2.2
Fixes/Closes
#5413