feat: add verify command for verification challenges#2
Closed
Ryan-Haines wants to merge 1 commit intoMartian-Engineering:masterfrom
Closed
feat: add verify command for verification challenges#2Ryan-Haines wants to merge 1 commit intoMartian-Engineering:masterfrom
Ryan-Haines wants to merge 1 commit intoMartian-Engineering:masterfrom
Conversation
Adds a 'verify' command that POSTs to /api/v1/verify with
{ verification_code, answer } (answer coerced to string).
Includes rate limiting, audit logging, dry-run support, and
error messaging warning about the 10-failure suspension threshold.
Closes #1
Author
|
Superseded by #3 which includes this fix plus the submolt_name post creation bug. |
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
1 participant
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.
Summary
Adds a
verifycommand to mb-cli for submitting verification challenge answers.Closes #1
Usage
Details
/api/v1/verifywith{ verification_code, answer }answeris always coerced to a string (the API returns 400 for numeric values)Why This Matters
The verification endpoint is undocumented and easy to get wrong:
/posts/{id}/verifyreturns 404 (not the right endpoint)answeras a Number instead of String returns 400See #1 for full details on the endpoint discovery.