Skip to content

Conversation

@Cherrypick14
Copy link
Contributor

@Cherrypick14 Cherrypick14 commented Aug 1, 2025

🎯 Overview

This PR implements the Report Rejection functionality as requested in issue #73 , allowing validators to reject research reports with proper validation and authorization.

Features Implemented

API Endpoint

  • POST /report/reject - New endpoint for rejecting reports
  • Comprehensive input validation using garde framework
  • Proper error handling with appropriate HTTP status codes

Request/Response Structure

// Request
{
  "report_id": "uuid",
  "reason": "duplicate_report|incomplete_information|already_known|out_of_scope",
  "validator_notes": "Optional notes (max 1000 chars)",
  "validated_by": "0x..." // Starknet wallet address
}

// Response
{
  "message": "Report rejected successfully",
  "report_id": "uuid"
}

@Cherrypick14
Copy link
Contributor Author

@ONEONUORA , I had opened the PR for the reject report feedback (#115 ). Please review when you get a chance.

@Cherrypick14 Cherrypick14 mentioned this pull request Aug 9, 2025
- Add allow(dead_code) attribute to Report struct fields that are part of database schema
- Run cargo fmt to ensure consistent code formatting
- All tests still passing (77/77)
- Regenerate .sqlx/ metadata with test queries included
- This resolves all SQLx offline compilation errors
- IDE red lines should now be completely resolved
@Cherrypick14
Copy link
Contributor Author

@ONEONUORA Please review this implementation when you get a chance! The report rejection feature is fully implemented and tested.

Copy link
Contributor

@ONEONUORA ONEONUORA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice implementation @Cherrypick14

@ONEONUORA ONEONUORA merged commit de4ccb3 into skill-mind:master Sep 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants