Skip to content
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

[BUG] The "computeTravelTimeFor" parameter not available in RouteDirectionOptions class #47257

Open
jwangga opened this issue Nov 19, 2024 · 6 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Maps needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@jwangga
Copy link

jwangga commented Nov 19, 2024

Library name and version

Azure.Map.Routing 1.0.0-beta3

Describe the bug

I need to use the "computeTravelTimeFor" parameter when requesting for route directions, but I am unable to find it in the RouteDirectionOptions class. is it a missing or exposed somewhere else in the library?

Thanks.

Expected behavior

Expect to find the option in the RouteDirectionOptions class just like other URL parameters supported by in the Azure Map Route Directions Rest API

Actual behavior

Not available

Reproduction Steps

Create an instance of RouteDirectionOption class, and try to set the computeTravelTimeFor property. It is not available.

Environment

No response

@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Maps needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. labels Nov 19, 2024
Copy link

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @dubiety.

@dubiety dubiety self-assigned this Nov 20, 2024
@dubiety
Copy link
Member

dubiety commented Nov 20, 2024

Hi @jwangga,
In SDK, it's renamed to TravelTimeType, you can use TravelTimeType.All and TravelTimeType.None to specify computeTravelTimeFor value.
I'll close this issue, but feel free to re-open if you have any other questions. Thank you very much!

@dubiety dubiety closed this as completed Nov 20, 2024
@jwangga
Copy link
Author

jwangga commented Nov 20, 2024

@dubiety Thanks for your quick response. Yes, I found the TravelTimeType option. However, when I set it to All, the return object Response does not seem to contain: these values:

"noTrafficTravelTimeInSeconds"
"historicTrafficTravelTimeInSeconds"
"liveTrafficIncidentsTravelTimeInSeconds"

Based on the API, I expect to see these values when TravelTimeType is set to All. Please advise.

@dubiety dubiety reopened this Nov 21, 2024
@dubiety
Copy link
Member

dubiety commented Nov 21, 2024

Re-open for further investigation.
@jwangga , I'll get back to you soon!

@dubiety
Copy link
Member

dubiety commented Nov 21, 2024

Hi @jwangga , we've found the issue. We'll fix this issue in our next release around early Jan. Thank you for your patience!

@jwangga
Copy link
Author

jwangga commented Nov 21, 2024

@dubiety Thanks for the update. Look forward to the next release in Jan. I want to include the integration with Azure Map in our products in the next release scheduled for 1st quarter of 2025.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Maps needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

2 participants