Skip to content

feat: require the pollora/meta package - #490

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

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

Conversation

@ogorzalka

Copy link
Copy Markdown
Member

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

  • composer.json: pollora/meta ^0.1.
  • Removes what moved: src/Meta/{Application,Domain,Testing}, the WordPress adapters and MetaDiscovery (41 files), and the 13 unit test files that went with them (they live in the package, now without Laravel).
  • Stays in the framework: Pollora\Meta\Infrastructure\Laravel (provider, validator, doctor check, commands), config/meta.php, the Meta facade, HasTypedMeta, and their tests, plus the contract tests.
  • Class names are unchanged: surface.json is untouched and still passes, the classes now resolve from the package.

Checked: suite in sequence, 1700 passed (1886 before, minus the tests that moved); PHPStan clean; Pint; the 28 captures of pollora-test (pages, REST, bindings, editor data, artisan outputs, roles, doctor) are identical to the references taken before the extraction, with Meta served by the package.

Typed meta lives in pollora/meta: the accessor and the fluent record, the schemas, the UI
drivers, the WordPress adapters, the discovery and the conformance suite, with their tests.
The framework keeps the Laravel side: provider, validator, doctor check and commands.
@ogorzalka
ogorzalka merged commit 6175c3e into release/v13.36.1 Oct 15, 2026
10 checks passed
@ogorzalka
ogorzalka deleted the feat/require-meta-package branch October 15, 2026 14:06
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