Running composer install doesn't resolve undefined type error in cloned Laravel project

Question

I've cloned a Laravel project from Github, then I've run composer install for getting vendor folder. This folder has appeared but I also get weird red lines under each class that show Undefined Type errors. I also deleted the composer.lock and run composer update, but the errors are still there! Is there any other thing that I should do?

@Aro I can also find the ```'Illuminate\Foundation\Testing\DatabaseMigrations'``` file under the vendor folder but the error is still there. — Hanie Asemi, Jul 26 '22 at 11:15
@Aro Yes, also it isn't just for one class,it's happening for all classes. — Hanie Asemi, Jul 26 '22 at 11:18
Hm. It's very strange. Because I have installed project and I don't have problem with it. Maybe problem with IDE ? — Aro, Jul 26 '22 at 11:20
@Aro It's the link of my project! https://github.com/hanieas/Expense-Mgmt-Backend could you please check it out? — Hanie Asemi, Jul 26 '22 at 11:22
@brombeer The project is running perfectly, but the errors still are there. — Hanie Asemi, Jul 26 '22 at 11:44

score 0 · Answer 1 · answered Jul 26 '22 at 12:21

The project was running perfectly, So I found out it was because of my IDE. The VS Code wanted to validate code using php, and it is not finding php installed. It's solved by setting php.validate.executablePath in Vs Code setting. For more information: "Cannot validate the php file. The php program was not found"

Running composer install doesn't resolve undefined type error in cloned Laravel project

1 Answers1