Skip to content

refactor: keep typed meta free of Laravel before it becomes a package - #488

Merged
ogorzalka merged 1 commit into
release/v13.36.1from
refactor/meta-ports
Oct 15, 2026
Merged

ogorzalka merged 1 commit into
release/v13.36.1from
refactor/meta-ports

Conversation

@ogorzalka

Copy link
Copy Markdown
Member

Step 1 of the extraction of pollora/meta (plan: .claude/plans/meta-roles-bindings-packages.md in pollora-test).

  • MetaUiDrivers, MetaAccessor::extend(): PSR-11 ContainerInterface instead of Laravel's Container (get() autowires under Laravel, so a driver given by class name is built as before; a closure receives the same container object).
  • MetaSchemaBuilder: Naming::snake() from pollora/attributes (same result as Str::snake(), as its docblock says) instead of Str.
  • MetaUiDriverConformance builds drivers with its own tiny PSR-11 container (InstantiatingContainer), no Illuminate.
  • What needs Laravel moves to Pollora\Meta\Infrastructure\Laravel: provider, LaravelMetaValidator, TypedMetaCheck, the two commands. These stay in the framework when the package is extracted.
  • surface.json regenerated: the diff is exactly the moved classes and the container type.

Checked: contract tests and Meta unit tests green, PHPStan clean, Rector + Pint; the 28 captures of pollora-test (pages, REST, bindings, editor data, artisan outputs, roles, doctor) are identical to the references taken before the change.

MetaUiDrivers and MetaAccessor::extend() take a PSR-11 container, the key of a data
object's property comes from Naming::snake(), the conformance suite builds drivers with
its own container, and what needs Laravel (provider, validator, doctor check, commands)
moves to Pollora\Meta\Infrastructure\Laravel. Pages, REST responses and command outputs
of pollora-test are identical to the references taken before.
@ogorzalka
ogorzalka merged commit 2b24b24 into release/v13.36.1 Oct 15, 2026
10 checks passed
@ogorzalka
ogorzalka deleted the refactor/meta-ports branch October 15, 2026 13: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