Repository navigation
Align Tessie vehicle methods with the current Tessie API docs - #227
Conversation
|
Warning Review limit reachedYour organization has reached its usage spending cap. Adjust your spending cap in the billing tab. Next included review available in 39 minutes. View limit details
|
Code Review ✅ Approved 🟡 Medium riskChanging set_drive_tag to send comma-separated drive IDs could cause the Tessie API to apply tags to unintended drive records. Aligns Tessie vehicle methods with the current Tessie API reference, adding VerificationRules No rules evaluated Functional validation Not enabledAuto-approval Approved For more verification details, comment OptionsAuto-apply is off → Gitar will not commit updates to this branch. Comment with these commands to change the behavior for this request:
Important Your trial ends in 7 days — upgrade now to keep code review, CI analysis, auto-apply, custom automations, and more. Was this helpful? React with 👍 / 👎 | Gitar |
Brings the Tessie vehicle methods back in line with Tessie's API reference. Adds
tessie_release_notes()(named with thetessie_prefix becauserelease_notes(staged, language)is already inherited from the Fleet API proxy and an override would break positional callers) androles().firmware_alerts()gains optionalstart/end.set_drive_tagnow sendsdrivesas the documented comma-separated string instead of a JSON array.drivestypesexclude_tagandexclude_driver_profileasbool | None.map()could never work because the endpoint returns a PNG and the request layer only reads JSON: it now returnsbytesthrough a new GET-only_request_byteson the shared client, which leaves_requestuntouched, so no other caller changes behaviour, andmarker_sizeis anint.format="csv"is still unsupported and is now noted in the docstrings anddocs/tessie.md. All existing signatures stay backward compatible;docs/tessie.mdandtests/test_tessie_vehicle_params.pyare updated, and the version is not bumped.