Conversation
Add `bodyEncoding: "json" | "form"` field to the fetch step schema.
Default is "json" (current behavior, nothing breaks).
When "form":
- Serializes body as URL-encoded key=value pairs (URLSearchParams)
- Sets Content-Type to application/x-www-form-urlencoded
- Template interpolation ({{variables}}) still resolves before encoding
Also updated httpPost/httpPut/httpPatch in check-context to:
- Respect Content-Type from passed headers (don't override with JSON)
- Send string bodies as-is (don't double-stringify form-encoded data)
This unblocks OAuth2 client_credentials flows (Sophos, ADP,
ServiceNow, etc.) and any legacy API requiring form-encoded POST.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
feat(integration-platform): add bodyEncoding option to fetch step
PR SummaryMedium Risk Overview TipTap validation is expanded to handle real-world malformed content. The validator now parses stringified JSON nodes, fixes malformed lists by wrapping/merging orphaned Integration DSL fetch steps gain form body support. Written by Cursor Bugbot for commit e4fb01a. This will update automatically on new commits. Configure here. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
[dev] [Marfuen] mariano/eng-197-when-going-in-a-policy-getting-a-node-with-invalid-content
…r token refresh buildHeaders was called once outside the request lambda, capturing the current auth token. On 401 retry after token refresh, executeRequest re-invokes the lambda but the stale token was reused. Moved buildHeaders inside the lambda for httpPost, httpPut, and httpPatch so each retry picks up the refreshed currentAccessToken. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
fix(integration-platform): move buildHeaders inside request lambda for token refresh
Updated PolicyEditorWrapper to include isPending state from usePermissions, allowing the editor to remain editable while permissions are loading. This prevents premature locking of the editor when checking for update permissions.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
apps/app/src/app/(app)/[orgId]/policies/[policyId]/editor/components/PolicyDetails.tsx
Outdated
Show resolved
Hide resolved
…er (#2400) Removed isPending state from usePermissions in PolicyEditorWrapper to streamline the logic for determining the editor's read-only state. This change ensures that the editor's lock state is based solely on the user's update permissions, enhancing clarity and maintainability. Co-authored-by: Mariano Fuentes <marfuen98@gmail.com>
|
🎉 This PR is included in version 3.13.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
3 participants
This is an automated pull request to release the candidate branch into production, which will trigger a deployment.
It was created by the [Production PR] action.