Allow for more flexible / configurable stripping behaviour. #4829
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.
Makes stripping behaviour bit more configurable, by removing the restriction of requiring AXIS property, while also allowing to define the way stripped state should be created.
Existing StrippableBlockRegistry#register(Block input, Block stripped) still only copies AXIS property.
A new StrippableBlockRegistry#registerCopyState(Block input, Block stripped) makes it copy all compatible properties.
If someone needs bit more control, they can use StrippableBlockRegistry#register(Block input, Block stripped, StrippingTransformer transformer) to define how and what is copied.