Mark Scherer

I agree, those things are easier to be detected with AST, like PHPStan and Psalm etc use. Maybe I have to look into some AST based solution here for those...

Any update on the PHP 8.1 compatibility? Our code seems to get ``` Deprecated: Return type of PDepend\Source\Language\PHP\PHPBuilder::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should...

I also do not see any harm in adding this PR You can still document the alternative of a fetchAllLazy and how it works, its pros and cons etc, separately.

Has this already been done in v3?

:+1: for some `diff` command to generate a migration from the current changes done to DB (like propel2 does).

Someone just has to take the idea and implement it. The leg work has already been done. There is a "snapshot" part available and based on that, the current migration...

What would be the use case for the first and last? Do you want to stub out a PR here?

ping @ajibarra Otherwise @swiffer you could also make a new PR from those changes and include the mentioned feedback Then we can merge an alternative PR here as well.

The same trick might also work here: https://github.com/cakephp/phinx/issues/1401#issuecomment-435210854

@markstory Any way we can do this?