Skip to content
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

feat: error classification #25

Merged
merged 1 commit into from
Jan 31, 2025
Merged

feat: error classification #25

merged 1 commit into from
Jan 31, 2025

Conversation

jboix
Copy link
Member

@jboix jboix commented Jan 30, 2025

Description

Resolves #21 by implementing server-side error classification based on content restrictions and refactoring the deserialization logic into a converter-based strategy:

Changes Made

  • Errors are now categorized using the new error_type field, and a business_error flag distinguishes between expected (business) errors and player errors.
  • Moved from a deserializer-based approach to a converter, enabling a more extensible processing pipeline.
  • Introduced a processing pipeline to standardize how different processors apply transformations.

Checklist

  • I have followed the project's style and contribution guidelines.
  • I have performed a self-review of my own changes.
  • I have made corresponding changes to the documentation.
  • I have added tests that prove my fix is effective or that my feature works.

@jboix jboix requested a review from MGaetan89 January 30, 2025 15:55
@jboix jboix self-assigned this Jan 30, 2025
Copy link

github-actions bot commented Jan 30, 2025

Coverage Report

Overall Project 66.1% -0.67% 🍏
Files changed 97.4% 🍏

File Coverage
EventRequest.kt 100% 🍏
ErrorProcessor.kt 99.13% -0.87% 🍏
UserAgentProcessor.kt 95.95% -4.05% 🍏
EventRequestDataConverter.kt 95% -5% 🍏
DataProcessor.kt 0% 🍏

@jboix jboix force-pushed the feat/error-classification branch 3 times, most recently from c451226 to b1e7313 Compare January 30, 2025 16:00
Resolves #21 by implementing server-side error classification based on content restrictions and
refactoring the deserialization logic into a converter-based strategy:

- Errors are now categorized using the new `error_type` field, and a `business_error` flag
  distinguishes between expected (business) errors and player errors.
- Moved from a deserializer-based approach to a converter, enabling a more extensible processing
  pipeline.
- Introduced a processing pipeline to standardize how different processors apply transformations.

Co-authored-by: Gaëtan Muller <[email protected]>
@jboix jboix force-pushed the feat/error-classification branch from b1e7313 to 939e68d Compare January 31, 2025 11:14
@jboix jboix requested a review from MGaetan89 January 31, 2025 11:14
@jboix jboix added this pull request to the merge queue Jan 31, 2025
Merged via the queue into main with commit 703a44c Jan 31, 2025
1 check passed
@jboix jboix deleted the feat/error-classification branch January 31, 2025 12:26
Copy link

🎉 This PR is included in version 3.2.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement error classification flag to distinguish business and critical errors
2 participants