fix: PruneCommand finding its usage within other traits (#42350)

This addresses an edge case where using the Prunable trait within another trait (due to several reasons like modifying behaviour, removing duplication, etc..) it was breaking the PruneCommand from behaving properly ince the trait was being detected as a class.

Signed-off-by: Bruno Gaspar <[email protected]>

src/Illuminate/Database/Console/PruneCommand.php

@@ -87,7 +87,9 @@ public function handle(Dispatcher $events)
     protected function models()
     {
         if (! empty($models = $this->option('model'))) {
-            return collect($models);
+            return collect($models)->filter(function ($model) {
+                return class_exists($model);
+            })->values();
         }
 
         $except = $this->option('except');
@@ -111,6 +113,8 @@ protected function models()
                 });
             })->filter(function ($model) {
                 return $this->isPrunable($model);
+            })->filter(function ($model) {
+                return class_exists($model);
             })->values();
     }
 

tests/Database/PruneCommandTest.php

@@ -89,6 +89,16 @@ public function testNonPrunableTest()
         $this->assertEquals(<<<'EOF'
 No prunable [Illuminate\Tests\Database\NonPrunableTestModel] records found.
 
+EOF, str_replace("\r", '', $output->fetch()));
+    }
+
+    public function testNonPrunableTestWithATrait()
+    {
+        $output = $this->artisan(['--model' => NonPrunableTrait::class]);
+
+        $this->assertEquals(<<<'EOF'
+No prunable models found.
+
 EOF, str_replace("\r", '', $output->fetch()));
     }
 
@@ -227,3 +237,8 @@ class NonPrunableTestModel extends Model
 {
     // ..
 }
+
+trait NonPrunableTrait
+{
+    use Prunable;
+}