-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Overwrite rerouting logic #16
Conversation
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.
Just some typos
/** | ||
Allows to customise the calculation of a route. | ||
|
||
If you want to overwrite the defult rerouting loigc, return true. |
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.
If you want to overwrite the defult rerouting loigc, return true. | |
If you want to overwrite the default rerouting logic, return true. |
|
||
If you want to overwrite the defult rerouting loigc, return true. | ||
|
||
- parameter from: The current olocation of the user |
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.
- parameter from: The current olocation of the user | |
- parameter from: The current location of the user |
|
||
- parameter from: The current olocation of the user | ||
- parameter along: The route progress | ||
- parameter completion: Callbackc function when either the route was sucessfully caluclated or if there was an error |
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.
- parameter completion: Callbackc function when either the route was sucessfully caluclated or if there was an error | |
- parameter completion: Callback function when either the route was successfully calculated or if there was an error |
- parameter from: The current olocation of the user | ||
- parameter along: The route progress | ||
- parameter completion: Callbackc function when either the route was sucessfully caluclated or if there was an error | ||
- return: True to preferent the route controller from running its own rerouting logic |
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.
- return: True to preferent the route controller from running its own rerouting logic | |
- return: True to prevent the route controller from running its own rerouting logic |
Thanks, I just found the spellchecker in XCode, I will try my best to improve the spelling :) |
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.
Sorry for the delay in reviewing this, but this looks good! Can't wait to try it out! Thanks @boldtrn!
Thanks for the review @ianthetechie, I will go ahead and merge this PR. |
This changes makes it possible to write custom rerouting logic in your app without requiring to use Mapbox directions.