demonstrate similarity for discussion purposes #18126
Closed
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 is a demonstration rather than an actual PR.
There is some very similar logic in
internals.make_block
andinternals.form_blocks
. For demonstration this PR separates the relevant bits out into_get_block_klass
andget_block_type
, respectively.Suppose that the small differences in these two new functions were reconciled. Then adding a custom block type would be a matter of adding it to
_block_type_klasses
along with registering some kind of hook in_get_block_klass
.There would need to be some cleanup at the end of
form_blocks
to map block types to_foo_blockify
functions.ref #17144
noci