refactor: Replace direct error responses with a consistent error response handler in payment processing #51
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.
This pull request refactors error handling and response encoding in the
OrderHandlerandPaymentHandlerclasses to improve code consistency and maintainability. The changes replace direct calls tohttp.Errorwith reusable helper methods and adjust variable naming for clarity.Refactoring Error Handling:
internal/interfaces/api/handler/payment_handler.go: Replacedhttp.Errorcalls withh.writeErrorResponsefor consistent error handling across multiple methods (CapturePayment,CancelPayment,RefundPayment,ForceApproveMobilePayPayment). Additionally, introducedh.handleValidationErrorfor validating request body errors inForceApproveMobilePayPayment. [1] [2] [3] [4] [5] [6] [7] [8]Response Encoding Adjustment:
internal/interfaces/api/handler/order_handler.go: Renamed the variableorderDTOtoresponsefor clarity and consistency in theUpdateOrderStatusmethod.