Thanks 👍

Can you also add test fixture that verifies this change? Just so we don't accidentally change it in the future.

It's already testing by the existing annotation fixture---I didn't want to write a whole PHPStan extension just to test something other than a AnnotationMethodReflection (e.g., Laravel's macro system)

No need for extension. What is "non-native method" apart the @method?

This is a Macro:

MenuItem::macro('reportable', static function (string $class): MenuItem {
    if (! class_exists($class) || ! is_a($class, Reportable::class, true)) {
        throw new RuntimeException("Invalid reportable class [{$class}].");
    }

    $instance = resolve($class);

    return MenuItem::make($instance->name())
        ->canSeeWith($instance::permissions())
        ->path($instance->route());
});

See: https://github.com/larastan/larastan/blob/3.x/src/Methods/MacroMethodsClassReflectionExtension.php

So in short, the reportable() does not exist?

Yes, it's not an actual method, it's a closure that is called through __call: https://github.com/laravel/framework/blob/12.x/src/Illuminate/Macroable/Traits/Macroable.php

Note, this does not actually result in a php error, so I'm not sure why phpstan added a check for it. I'm thinking about just globally ignoring callable.nonNativeMethod, but I figured that rector should not make changes that result in phpstan errors

I see. How would you implement it if no Rector nor PHPStan would exists?

I'm not sure what you're asking? Implement what?

The change this rule is doing. How would you upgrade code yourself manually, without any tooling.

I would be fine with this upgrade in favor of the first class callable, however, other people might not like it since it throws phpstan errors.

This PR just ensures that an actual method exists on the declaring class and that the method in not a macro or annotation

Allright, lets go this way then.

We still need a test fixture to backup this change.