Payment DTO improvements #16
Merged
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 introduces a new release (version 3.4.3) across all modules and significantly extends the
AccountPaymentDTOdata transfer object to support more payment-related attributes. It also updates theAccountPaymententity to ensure all new DTO fields are properly populated, and refines some UI action properties for better clarity and consistency.DTO and Entity Enhancements:
AccountPaymentDTO(such asaccount,paymentMethod,couponCode,externalReference,invoiceNumber,reseller, etc.) to capture more detailed payment information. Corresponding getters and setters were implemented. [1] [2] [3] [4]AccountPaymententity'stoDTO()method to populate all new DTO fields, ensuring that related entity data (like payment method, additional service, account, and reseller) is transferred to the DTO.Project Version Updates:
pom.xmlfiles across the project, including parent, API, core, JPA, remote, and UI modules, to mark the new release and ensure dependency consistency. [1] [2] [3] [4] [5] [6] [7] [8] [9]UI Improvements:
NewAccountPaymentActionUI action to usesetShowLabel(true)instead of setting the attribute directly, removed deprecated color/background settings, and set the action type to"success"for better semantic clarity.Code Cleanup:
AccountPayment.javafor clarity and to remove unused wildcard imports.These changes collectively enhance the extensibility and maintainability of the payment module, provide richer data transfer capabilities, and ensure the UI and project structure are up to date with the latest standards.