[alies-dev]

Blade components pass their zero-argument public methods to views wrapped in \Illuminate\View\InvokableComponentVariable instances, and so far static analysis tools couldn't infer return types of such InvokableComponentVariable, so I'm proposing to use @template syntax for InvokableComponentVariable.

PR adds a single covariant template for the resolved value and declares it as a mixin, so a view can state what a component method returns and both calling it and proxied access are typed:

@php /** @var \Illuminate\View\InvokableComponentVariable<\Illuminate\Support\Collection<int, \App\Models\Plan>> $plans */ @endphp

{{ $plans->count() }} plans {{-- int instead of an undefined method --}}

@foreach ($plans() as $plan)
    {{ $plan->name }} {{-- $plan is App\Models\Plan instead of mixed --}}
@endforeach

The change is PHPDoc only. The template defaults to mixed, so existing unparameterized InvokableComponentVariable annotations keep working.

tools

Additionally bladestan may implement custom handlers to specify more narrow return types instead of mixed; psalm/plugin-laravel already does.

[github-actions]

Thanks for submitting a PR!

Note that draft PRs are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface.

Pull requests that are abandoned in draft may be closed due to inactivity.