-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolves several code issues #287
Merged
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
cammace
added
✓ ready for review
and removed
⚠️ DO NOT MERGE
PR should not be merged!
labels
Sep 29, 2017
zugaldia
approved these changes
Sep 29, 2017
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's bring back STEP_MANEUVER_TYPE_*
, otherwise, 👍 .
Grsmto
pushed a commit
to Grsmto/mapbox-navigation-android
that referenced
this pull request
Oct 2, 2017
* master: Resolves several code issues (mapbox#287) removed OSRM-Text-Instructions (mapbox#288) readme bump to 0.6.1 (mapbox#282) 0.6.1 Release (mapbox#283) fix navigation events so that use the correct sdk identifier depending on where they come from (navigation or navigation-ui) (mapbox#277)
Grsmto
pushed a commit
to Grsmto/mapbox-navigation-android
that referenced
this pull request
Oct 3, 2017
* grs-fix-offroute-false-positive: (50 commits) add missing imports offroute detector should get the right upComingStep instead of the last step of the leg to do the calculation Resolves several code issues (mapbox#287) removed OSRM-Text-Instructions (mapbox#288) readme bump to 0.6.1 (mapbox#282) 0.6.1 Release (mapbox#283) fix navigation events so that use the correct sdk identifier depending on where they come from (navigation or navigation-ui) (mapbox#277) fix a bug where the snappedPoint lat/lng values are infinity if the step geometry is a single point (for example the last step of a leg) instead of a line string we don't need to enter in this condition if isOffRoute is false fix mockNavigation activity waypoints adding order + zoom level for easier testing add offroute event listener on mockLocation activity, so we can test this bumped version # in readme (mapbox#267) Release 0.6 (mapbox#262) Don't remove milestone listener on arrival / adjust arrival verbiage Update Camera tilt and MAS dependency (mapbox#261) unknown profile (mapbox#259) Bump up Navigation UI example / change log position (mapbox#260) Reduce Reroute Threshold (mapbox#251) Camera and location layer ignore null location (mapbox#252) User agent plus exit roundabout (mapbox#250) ... # Conflicts: # navigation/libandroid-navigation/src/main/java/com/mapbox/services/android/navigation/v5/navigation/DefaultMilestones.java # navigation/libandroid-navigation/src/main/java/com/mapbox/services/android/navigation/v5/navigation/NavigationHelper.java
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.
Issues which will eventually be affected by new checkstyle rules and some of the SonarCloud issues