Migrations/Schema scanning does not take into account multiple connections

[calebdw]

• Larastan Version: 9.X
• --level used: 1
• Pull request with failing test:

Description

Hello!

It seems that Larastan does not respect multiple connections. I have two different connections (or databases) with a users table---their models have the $connection property in them so everything works.

However, when Larastan is scanning the migrations/schemas for the table properties it just puts all of the tables into an array keyed by the table name so one of the tables is overwritten (and therefore Larastan is throwing undefined property errors for that model).

Laravel code where the issue was found

        if ($creating) {
            $this->tables[$tableName] = new SchemaTable($tableName);
        }

[szepeviktor]

Yes, you're right. Larastan supports 1 database.