Closed Udumft closed 1 year ago
So I've updated TollPrice
to the flat representation. It should be easier to read and understand for developers and it still has some possibilities for foreignMembers
coding. It is capable of detecting new types of payment methods and new categories. New parameters are handled on the toll price object itself, but it won't handle new properties anywhere else.
It is capable of detecting new types of payment methods and new categories. New parameters are handled on the toll price object itself, but it won't handle new properties anywhere else.
I think this is consistent with the JSON format. In case the API introduces new payment methods or vehicle categories that we don’t recognize, TollPaymentMethod
and TollCategory
are both extensible enumerations; the unrecognized values would just be strings without symbols.
The PR adds
Route.tollCosts
andRouteOptions.computeTollCost
for requesting and working with toll fees. Marking new properties and types with:nodoc:
and skipping CHANGELOG update since it is a private API feature.