Skip to content

feat: v3.1.0 - workflow support in patch_item & HTTP client improvements#13

Merged
veer-shipthis merged 1 commit intomainfrom
feat/v3.1.0-workflow-patch
Mar 27, 2026
Merged

feat: v3.1.0 - workflow support in patch_item & HTTP client improvements#13
veer-shipthis merged 1 commit intomainfrom
feat/v3.1.0-workflow-patch

Conversation

@mayurrawte
Copy link
Copy Markdown
Member

Summary

  • Workflow transitions in patch_item — supports direct-mode (value) and action-based (action_id) workflows, can be combined with field updates in a single call
  • Persistent HTTP client — reuses httpx.AsyncClient across requests instead of creating one per call (connection pooling, fewer TLS handshakes)
  • Async context managerasync with ShipthisAPI(...) as client: for automatic cleanup
  • Fixed query param encodingget_exchange_rate, search_location, get_place_details now use query_params dict instead of string interpolation
  • Proper disconnect() cleanup — now async, closes HTTP client, clears all state

Test plan

  • Verify patch_item with update_fields only (backward compat)
  • Verify patch_item with workflow only (direct mode)
  • Verify patch_item with workflow only (action-based)
  • Verify patch_item with both update_fields + workflow
  • Verify async with context manager lifecycle
  • Verify upload_file still works (separate client)
  • Verify third-party methods with special characters in params

…p to v3.1.0

- Support workflow transitions in patch_item (direct-mode and action-based)
- Reuse HTTP client across requests for connection pooling
- Add async context manager support
- Fix query param URL encoding in third-party methods
- Properly clean up state in disconnect()
@veer-shipthis veer-shipthis merged commit a973e5d into main Mar 27, 2026
3 checks passed
@mayurrawte mayurrawte deleted the feat/v3.1.0-workflow-patch branch March 27, 2026 07:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants