README

Dynamic property typing is read-only; the trait has no setter contract. Real properties keep their native types, and only native getters count, not @method declarations. Trait use is followed through parent classes and nested traits. Overrides of __get, meta, has_custom_getter or call_custom_getter are left to their declared behaviour, and the getter argument resolution hook may still be overridden, as PressGang supports.

meta() needs a single known, nonempty constant string. Dynamic keys, unknown getters, uncertain unions, argument unpacking and the falsey keys '' and '0' retain the declared return type. Getter dispatch happens before Timber's parent meta processing, so transform_value options don't change a custom getter's return type. Ordinary ACF fields stay as declared, usually mixed — this package won't invent field shapes from runtime configuration.

Manifest references are registered with PHPStan's unused-method extension point. That describes declared manifest usage; it doesn't make all controller methods used, or replace third-party dead-code tools' own call graphs.

Non-Timber base class? Extensions register against classes, not traits, so the default is Timber\CoreEntity. For your own base class, register another instance:

services:
    -
        class: PressGang\PHPStan\Type\MetaReturnTypeExtension
        arguments:
            baseClass: Your\ModelBase
        tags:
            - phpstan.broker.dynamicMethodReturnTypeExtension

The property and recursion extensions already apply to every trait user. AbstractController doesn't currently use HandlesDynamicGetters itself.

includes:
    - vendor/pressgang-wp/phpstan/rules.neon

pressgang.contextGetterOrphan reports get_*() methods absent from a concrete controller's effective manifest, including inherited and trait methods. get_context() and get_template_candidates() are excluded, and abstract controllers aren't assessed — they can supply getters for child manifests.

It's advisory: direct calls, hooks and framework lifecycle calls can all use a getter without a manifest entry. Mark intentional helpers on the method:

/**
 * Called by get_featured_posts(), so it never appears in the manifest.
 *
 * @pressgang-context-helper
 */
protected function get_excerpt_length(): int {
    return 40;
}

PHPStan has no separate warning severity, so opting in makes these diagnostics count toward its exit status. The annotation suppresses only this advisory — missing-method and recursion diagnostics are unaffected. Don't remove methods on this advice alone; absence from a manifest doesn't itself execute a query.

Nothing to configure: analysing src already covers src/Blocks. Block subclasses use ordinary static get_context() and render() methods, so PHPStan checks those calls and overrides directly.

The gotcha: blocks don't use controller manifests, so block get_*() helpers never need @pressgang-context-helper — the orphan rule leaves them alone.

Model getters behave exactly as they do anywhere else, including inside a block:

abstract class BaseBlock extends \PressGang\Blocks\Block {
    /**
     * @param array<string, mixed> $block
     * @return array<string, mixed>
     */
    protected static function get_context(mixed $block): array {
        $context = parent::get_context($block);        // array<string, mixed>
        $context['subtitle'] = (new Page())->subtitle; // still a string
        return $context;
    }
}

Document a custom get_context() as array<string, mixed> in and out, keeping the framework's native mixed parameter. Inherited implementations, trait helpers and deliberately replaced contexts are all supported — calling parent::get_context() isn't mandatory.

The extension doesn't promise a fixed block-context shape: ACF fields can replace context keys, and their values depend on runtime field configuration. Block registration, callback wiring and template discovery still need runtime checks.

The manifest resolver reads source-reflected property defaults and treats a child declaration as a replacement, not a merge; unresolvable or non-string defaults are skipped. It doesn't model constructor mutations, runtime filters, dynamic manifest assignment, indirect call graphs, recursive cycles across multiple getters, or closures passed elsewhere. The recursion rule detects direct $this->meta() calls in the current getter, including constant expressions and named arguments, and skips nested closure bodies and overridden dispatch.

Config, snippets, bootstrap wiring and installed namespaces belong to wp capstan doctor. Config shape maps and Twig/template validation are out of scope. This package loads neither PressGang nor Timber at runtime — consumers provide their installed framework for reflection.

composer install
composer update phpstan/phpstan:2.2.9  # validate the supported minimum
composer check                         # PHPUnit + level-8 PHPStan + WordPress PHPCS

Tests mirror tests/Unit in PressGang and use PHPStan's RuleTestCase and TypeInferenceTestCase rather than booting WordPress — see the testing guide. The isolated trait fixture is copied from PressGang's current HandlesDynamicGetters; keep it in sync when that contract changes. Fixtures cover aliases, numeric keys, parent and trait getters, inherited and replaced manifests, orphan opt-outs, recursion, native properties, overridden dispatch, nullable and generic types, and fallback meta calls.

The optional fixture at tests/integration/timber.php runs generic model and controller classes against real Timber and PressGang dependencies. It intentionally produces five diagnostics: an array subtype overclaim, an undefined Term property, a collection return mismatch, a missing manifest getter and a recursive meta getter. Getter-backed property and meta type assertions must pass. Run it from a consuming theme, using a config without a baseline or theme-specific ignores:

vendor/bin/phpstan analyse -c /path/to/integration.neon --memory-limit=1G \
  /path/to/pressgang-phpstan/tests/integration/timber.php