Repository navigation
Agent-authored Slack Block Kit components in respond_to_user #23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
055a9de
Add agent-authored Slack Block Kit components to respond_to_user
josephschorr 1dc48bb
Address PR #23 review: harden Slack Block Kit component paths
josephschorr 8939347
Reject broadcast/usergroup mentions in all data_viz chart labels
josephschorr 038ab06
Close the gaps from the PR #23 re-review of Slack Block Kit components
samkim File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"blocks": []/"blocks": nullnow fail the call.len(in.Blocks) > 0is true for the raw bytes[]andnull. On a non-components channel the model gets "blocks are not supported", and on Slack it gets "must contain at least one block" or "must be a JSON array". Before this change these were ignored. Models often send empty optional arrays, so a plain-text reply now errors and costs a retry turn. Treat trimmednull/[]as absent.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed —
respond_to_usernormalizesblocksright after parsing vianormalizeOptionalBlocks: a trimmed""/null/[]becomes absent (nil), so an empty optional array no longer errors a plain-text reply. The single normalization covers every downstream check (not-supported guard, blocks+attached combo, validator, leakage projection, strip/publish, log flag), since they all key offlen(in.Blocks) > 0.