Document known issues for RMA in Adobe Commerce #475
Merged
Conversation
This file contains 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 MR documents every issues we found in Magento when working on supporting Adobe Commerce RMA feature.
We decided to use workarounds for some of them until they're fixed in Adobe Commerce, but it is important to explicitly document this.
I also documented a known issue from the core even though it is patched by our Front-Commerce Magento module, as the patching process may be broken in some projects.
Preview: https://deploy-preview-475--heuristic-almeida-1a1f35.netlify.app/docs/magento2/commerce#rma