Fix Slack question-card membership request encoding - #98
Merged
Merged
Conversation
Signed-off-by: Tiberiu Socaci <tsocaci@makeitfuture.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Question cards failed to post because the live Slack membership check rejected a JSON POST with
invalid_arguments. Send membership reads as GET requests with encoded channel, limit and pagination cursor parameters, retaining JSON POSTs for chat writes.Validation: 40 focused question tests; full coverage suite (2,561 passed, 13 opt-in skipped); static, secret scan, security coverage, DCO and high-severity dependency gate passed. A live membership check and question-card post succeeded with the corrected transport. End-to-end human submission and dual-engine acceptance remain pending.