This repository was archived by the owner on Nov 19, 2024. It is now read-only.
Use a layout processor rather than plugin in the "Customize the view of a checkout step" docs #8373
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
…of a checkout step" docs
BarnyShergold
approved these changes
Dec 11, 2020
m2-community-project
bot
added
Progress: approved
and removed
Progress: ready for review
labels
dobooth
approved these changes
Jan 4, 2021
dobooth
added
2.4.x
|
running tests |
|
Hi @Serializator, thank you for your contribution! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Purpose of this pull request
Using a separate layout processor is preferred over an after or around plugin bound to the
Magento\Checkout\Block\Checkout\LayoutProcessorclass.I rewrote the documentation in regards to "Customize the view of a checkout step" so that it uses the layout processor approach rather than a plugin.
Affected DevDocs pages