Skip to content

feat: require the pollora/block-bindings package - #494

Merged
ogorzalka merged 1 commit into
release/v13.36.1from
feat/require-block-bindings-package
Oct 15, 2026
Merged

ogorzalka merged 1 commit into
release/v13.36.1from
feat/require-block-bindings-package

Conversation

@ogorzalka

Copy link
Copy Markdown
Member

Step 3 of the extraction of pollora/block-bindings (Pollora/block-bindings v0.1.0, on Packagist).

  • composer.json: pollora/block-bindings ^0.1.
  • Removes what moved: src/BlockBinding/{Application,Domain,UI}, the WordPress adapters, services and sources (24 files), resources/js/block-bindings.js (it ships with the package, which reads it from its own directory), and the 9 unit test files that went with them.
  • Stays in the framework: Pollora\BlockBinding\Infrastructure\Laravel (provider, LaravelMethodInvoker, LaravelBindingEvents, LaravelPostFinder, doctor check, commands and stub), config/block-bindings.php, the resolver and provider tests that exercise the Laravel container, and the contract tests.
  • Class names are unchanged: surface.json is untouched and still passes.

Checked: suite in sequence 1576 passed (1636 before, minus the tests that moved); pint --test on the whole tree, PHPStan and Rector clean; the 28 captures of pollora-test (bindings resolved over REST for four sets, editor data, binding:list, concert pages, roles, doctor…) are identical to the references taken before the extractions, with Block Bindings served by the package.

Block Bindings live in pollora/block-bindings: the resolver, the sources Pollora ships, the
discovery, the WordPress adapters, the editor script and the preview route, with their tests.
The framework keeps the Laravel side: provider, config, the Laravel contracts' implementations,
the doctor check and the commands.
@ogorzalka
ogorzalka merged commit 296f4c2 into release/v13.36.1 Oct 15, 2026
10 checks passed
@ogorzalka
ogorzalka deleted the feat/require-block-bindings-package branch October 15, 2026 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant