chore: Update platform types - #713
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bf8d796641
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "Codex (@codex) address that feedback".
| "minLength": 1, | ||
| "maxLength": 10000, | ||
| "description": "Instructions for Loop to format content sent to this destination" | ||
| "description": "Publish a Slack mrkdwn digest.\n\nInclude a complete \"*Pattern outcomes*\" section with one row for every selected Pattern from the run report, including created, updated, unchanged, failed, skipped, and newly inactive outcomes.\n\nUse this row format exactly:\n• <pattern_url|Pattern title> — `outcome`\n\nIf a Pattern has no URL, use the plain title instead. Do not use GitHub Markdown tables or code-block tables, because links must remain clickable. Do not omit any selected Pattern. If there are no selected Patterns, say \"No pattern outcomes.\"\n\nAfter the outcome list, include a \"*Highlights*\" section with one very short paragraph, 2-3 sentences maximum. Summarize what changed or what broadly stands out from this run. Do not introduce new claims beyond the run report." |
There was a problem hiding this comment.
For SDK users inspecting Slack actions on logs, environment_update, topic_digest, or generic windowed automations, this field is now documented with a Patterns-run output prompt even though those triggers do not necessarily have selected Patterns or pattern outcomes. The webhook sibling still describes the field generically, so the platform schema should explain that this value contains formatting instructions—or document the default separately—rather than embedding a Patterns-specific prompt across every Slack action before regenerating these types.
Useful? React with 👍 / 👎.
1 participant
Automated regeneration of SDK types.