Hpos compatibility #219
Merged
Hpos compatibility #219
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
|
Merged
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.
Reason for change
HPOS compatibility
Task
How to test
uninstall wmpl
In the admin go to Pages -> checkout -> edit
select the block
click on switch to classic checkout
click on update in top of the page
In Woocommerce admin : go to woocommerce -> settings -> advanced -> features
We can now enabled High Performance order storage and compatibility mode
Place alma orders
Then do a full refund with alma, partial refund and check if you have the notice on the right and the notice in the page
The title of the PR uses business wording, not technical jargon, for the changelog readers to understand it
The PR implements the changes asked in the referenced task / issue
The automated tests are compliant with the testing strategy
The tests are relevant, and cover the corner/error cases, not only the happy path
You understand the impact of this PR on existing code/features
The changes include adequate logging and Datadog traces
Documentation is updated (API, developer documentation, ADR, Notion...)