Uh oh!
There was an error while loading. Please reload this page.
userlog rte update alerts: good rtes + bad labels - #384
Merged
Conversation
This file contains hidden or 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
Sign up for freeto 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.
Some additions to userlog route update alerts per #189 (comment)
(assumes routes were previously connected; reports start/end of ConRte)
Alerts for some 6-field error types are not yet implemented:
Waypoint label... not foundandduplicate labelare the most sensible, and their 4-field counterparts are implemented. These are postponed pending a potential reorganization of that part of the code.Unknown region/highway combomight be going a bit overboard...Don't know what the merge conflict is all about. I'll see what I can see.