Repository navigation
Conversation
test: pin the URLs each asset container resolves, in build and hot
refactor: give the asset classes that will leave the framework their dependencies
feat: require the pollora/assets package
…ndings A snapshot of every class under src/Meta, src/Role and src/BlockBinding (name, parents, public and protected signatures, the fluent ones included), and three contract tests that run the real providers, the real Laravel container and real stores in memory: typed meta end to end, roles from attributes to stored capabilities, and Block Bindings over typed meta with the options a project lists in config. The extractions into packages must keep all of it.
test: contract tests for Meta, Roles and Block Bindings (before their extraction)
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.
refactor: keep typed meta free of Laravel before it becomes a package
The label of a #[Role] without one comes from Naming::headline(), and what needs Laravel (provider, middleware, @ROLE directive, doctor check, commands and stubs) moves to Pollora\Role\Infrastructure\Laravel. Roles, capabilities and command outputs of pollora-test are identical to the references taken before.
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.
refactor: keep roles free of Laravel before they become a package
feat: require the pollora/meta package
Roles and capabilities live in pollora/roles: the definition builder, the registry, the compiler, the WordPress adapters and the discovery, with their tests. The framework keeps the Laravel side: provider, middleware, @ROLE directive, doctor check and commands.
feat: require the pollora/roles package
… and network query facades
…ckage The resolver takes a PSR-11 container; two contracts carry what Laravel did for it (MethodInvokerInterface for the parameters of a source's method, BindingEventsInterface for BindingResolved); the options a project lists reach OptionSource and the editor data as an array; labels and names come from Naming; the Laravel side (provider, doctor check, commands) moves to Pollora\BlockBinding\Infrastructure\Laravel. Pages, REST responses and command outputs of pollora-test are identical to the references taken before.
BindingContext::post() asked the framework's Post model; a PostFinderInterface now gives it (the framework's Post under Laravel, Colt's without it), so the context no longer reaches the framework. The captures of pollora-test are still identical.
refactor: keep block bindings free of Laravel before they become a package
…for a minor release
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.
feat: require the pollora/block-bindings package
chore: accept pollora/query 2.0 alongside 1.x
chore: release v13.36.1
chore: release v13.36.1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Publishes v13.36.1 (see CHANGELOG): the four extractions (
pollora/assets,meta,roles,block-bindings) andpollora/query^1.0 || ^2.0.