This repository has been archived by the owner on Aug 16, 2022. It is now read-only.
fix: KML coordinates splitting #25
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
rot1024
approved these changes
Jul 16, 2021
Codecov Report
@@ Coverage Diff @@
## main #25 +/- ##
=======================================
Coverage 16.00% 16.00%
=======================================
Files 198 198
Lines 40002 40002
=======================================
Hits 6401 6401
Misses 32633 32633
Partials 968 968
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Overview
Fix the bug that KML coordinates were not decoded for "\t" separator
What I've done
replaced strings.Split() with strings.Fields() to cover all white spaces
What I haven't done
How I tested
separated coordinates for each white-space
Which point I want you to review particularly
Memo