Implement RMA export functionality and configuration settings#10
Draft
Implement RMA export functionality and configuration settings#10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 RMA (Return Merchandise Authorization) export feature, allowing RMA data to be exported to an external Faslet backend. It adds configuration options for RMA export, implements the core export service, and enhances configuration interfaces and repositories to support these features.
RMA Export Feature Implementation
ExportServiceclass inModel/Rma/ExportService.phpto handle exporting RMA entities to the Faslet backend, including payload building, event filtering, and webhook publishing.RepositoryInterfacefor RMA export enablement, endpoint URL, auth token, timeout, and lifecycle events.RepositoryInterfacewith methods to get/set RMA export settings and check which lifecycle events should be exported.Model/Config/Repository.php, including secure retrieval and decryption of the RMA auth token, and logic for handling lifecycle events.Configuration and Security Enhancements
BaseRepositoryto support decryption of sensitive config values (like the RMA auth token) by injecting and usingEncryptorInterface. [1] [2] [3]DataInterfaceand its implementation to allow fetching the shop ID for a specific store, improving multi-store support. [1] [2]