Skip to content

DEV: Unhide spam detection setting #1374

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 2 commits into from
May 28, 2025
Merged

DEV: Unhide spam detection setting #1374

merged 2 commits into from
May 28, 2025

Conversation

keegangeorge
Copy link
Member

@keegangeorge keegangeorge commented May 27, 2025

🔍 Overview

We want to unhide ai_spam_detection_enabled setting so that we can retain staff action log features. However, we also want to ensure users cannot enable spam detection without having AiModerationSetting.spam present in the database.

In this update we unhide the setting, but also add a validator to ensure the necessary configuration is in place before allowing the setting to be enabled.

Test is omitted as it's quite tricky to test. When test env is booted, it tries and validate all settings so we run into errors, before checking.

📷 Screenshots

Screenshot 2025-05-27 at 13 55 19

## 🔍 Overview
We want to unhide `ai_spam_detection_enabled` setting so that we can retain staff action log features. However, we also want to ensure users cannot enable spam detection without having `AiModerationSetting.spam` present in the database.

In this update we unhide the setting, but also add a validator to ensure the necessary configuration is in place before allowing the setting to be enabled.
@keegangeorge keegangeorge merged commit 297c64c into main May 28, 2025
6 checks passed
@keegangeorge keegangeorge deleted the dev-unhide-spam branch May 28, 2025 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants