-
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
NAVAND-547 route refresh for new annotations #7582
Conversation
ChangelogFeatures
Bug fixes and improvements
Known issues
|
Codecov Report
@@ Coverage Diff @@
## main #7582 +/- ##
=========================================
Coverage 74.15% 74.15%
- Complexity 6154 6156 +2
=========================================
Files 830 830
Lines 32936 32952 +16
Branches 3933 3935 +2
=========================================
+ Hits 24423 24437 +14
Misses 6978 6978
- Partials 1535 1537 +2
|
@@ -48,6 +48,16 @@ internal object AnnotationsRefresher { | |||
newAnnotation, | |||
startingLegGeometryIndex, | |||
) { maxspeed() } | |||
val freeFlowSpeed = mergeAnnotationProperty( |
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.
Some changes are also required in DirectionsRouteDiffProvider
.
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.
done
} | ||
newAlternatives.forEach { | ||
assertEquals( | ||
"some info was lost during NN -> Nav SDK transition", |
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.
?
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.
it means that info from response doesn't match the info we get from NN
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.
What does it have to do with the new annotation?
@@ -219,6 +219,8 @@ class AnnotationsRefresherTest( | |||
.distance(listOf(1.2, 3.4, 5.6, 7.8, 9.0)) | |||
.duration(listOf(11.2, 33.4, 55.6, 77.8, 99.0)) | |||
.speed(listOf(41.0, 42.5, 43.1, 44.6, 45.9)) | |||
.freeflowSpeed(listOf(1, 2, 3, 4, 5)) |
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.
Are you also gonna test it in instrumentation tests? I see a lot of room for error for NN team, they already said something would be wrong after refresh.
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.
Which test do you suggest?
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.
The same, but with NN involved. :)
We already have some tests that test annotations refresh, we could just extend them.
Description
Companion PR for mapbox/mapbox-java#1567