refactor(api-client): extract cloud task transport#3622
Conversation
|
React Doctor found no issues in the changed files. 🎉 Reviewed by React Doctor for commit |
533ed1f to
fe1c27f
Compare
c0ffe74 to
88a0684
Compare
4478f7e to
9932264
Compare
|
36ecfcf to
826b6dd
Compare
|
fixed the resume path so it always supplies the runtime adapter and preserves the selected permission mode. |
01d914f to
c5f360f
Compare
826b6dd to
df92334
Compare
a14c3b7 to
86e2b83
Compare
Generated-By: PostHog Code Task-Id: c1bbe3cf-742b-4b24-bf96-d11a18b4cf22
86e2b83 to
9bc38a5
Compare

Problem
Cloud-task transport behavior needed a host-neutral API client before mobile could stop maintaining its own HTTP implementation.
Depends on #3616
Refs #2416
Changes
Phase 1 only: I added the existing cloud-task, automation, integration, sandbox, and run transport to
@posthog/api-client, with normalization and contract tests. Mobile remains unchanged in this PR.How did you test this?
Automatic notifications
Created with PostHog Code