fix(flags): skip issuer iframe for board-choice flags#1
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThis PR implements a dual-path flag verification system. Country flags (issued by ChangesCountry vs Board-Choice Flag Verification Paths
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Verification
Note
Medium Risk
Changes publication-time challenge behavior for memeflags and pony flags (immediate allow vs prior signed assertion flow); country issuer verification path is unchanged but clients relying on challenge-emitted pol/pony data must use flair-only rendering.
Overview
Board-choice
/pol/and/mlp/flags no longer go through the issuer iframe or signedcomment["5chan"]path. After family allow-list and parsing checks,getChallengereturns immediate success for non-countryrequests; only country flags still require a community signer, lazy iframe URL, andPOST …/challenge/verify.README now separates issuer-verified country flags (immutable namespace + flair mirror) from memeflags/pony (clients publish normal flair; challenge only validates allowed family and known code).
Tests were updated to expect
{ success: true }withoutfetchfor pol/pony, and issuer mismatch coverage targets country verification only.Reviewed by Cursor Bugbot for commit 824287e. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by CodeRabbit
New Features
Documentation