[Platform] PoC trait for handling providers api errors #561
+109
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've created a simple trait to standardize HTTP response status code handling across different platform bridges. Currently, each bridge implements its own error handling, leading to inconsistent exception behavior and code duplication.
The ResultConverterStatusExceptionTrait
This trait provides:
Need feedback:
Is this trait approach the right way to standardize error handling? Or would you prefer a different pattern?
Should the trait be more or less opinionated about which status codes to handle?
Are there other common error patterns that should be included?
Is the naming appropriate and in line with conventions?
Depending on feedback, I plan to implement this in all ResultConverters to standardize error handling across platforms.