Send localizable ban response#1088
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 ignored due to path filters (1)
📒 Files selected for processing (3)
💤 Files with no reviewable changes (1)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughBan notices now use a structured {"command": "banned", "expires_at": ""} payload. LobbyConnection forwards error.response() to clients. Tests updated to assert the new payload and parse ISO timestamps. Minor qdatastream change converts a bytearray to bytes before packing. ChangesBan response and related updates
🎯 3 (Moderate) | ⏱️ ~20 minutes
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 |
Fixes #640
What: Sends a
bannedprotocol message with an ISOexpires_attimestamp instead of an English HTML notice.Why: The client can localize the ban message and format the timestamp itself.
Verification:
python -m py_compileon modified files.pytestwas not available locally.Summary by CodeRabbit