Automattic / Automattic/jetpack

Block Delimiter / Scanner: retire in favor of Core's upcoming WP_Block_Processor

Open
#45,519 0 comments 0 reactions 0 assignees View on GitHub
[Package] Block Delimiter [Pri] Normal
Dominant language
PHP
Stars
1.8k
Forks
898
Avg merge
1d 18h
Merged PRs (30d)
774

Description

We currently have a `Block_Scanner` and a `Block_Delimiter` class available in the Block delimiter package:
https://github.com/Automattic/jetpack/tree/trunk/projects/packages/block-delimiter

Since WordPress 6.9 will introduce a `WP_Block_Processor` class, we could switch to using it, and retire our package, **once Jetpack requires WordPress 6.9**.

Reference: https://core.trac.wordpress.org/ticket/61401

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the projects/packages/block-delimiter package and the WordPress 6.9 requirement for Jetpack. Trace where Block_Scanner and Block_Delimiter are used, then verify that the package can be retired and its uses switched to Core's WP_Block_Processor once the minimum WordPress version permits it.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
backend
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.