Closed jkudish closed 1 year ago
Seems like an issue you've encountered before #248
Upon further investigation, this seems to happen because vapor-core
includes some references to files found in laravel/octane
which isn't installed in my project. Normally, this isn't an issue as the vapor-core
package doesn't load the octane runtime unless explicitly set. However, as a result of Reflection, Invoker does try to find that namespace.
I don't know if Invoker has a blacklist of packages not to scan, but a possible solution would be ignore vapor-core
when scanning the vendor
folder. Rationale being that vapor-core
doesn't (and is unlikely to ever) have any models in it.
We added vapor-core
to our internal ignore-list and will release this in an upcoming version.
Heya,
I have some Models in my vendor folder that I wanted to include in Invoker so I turned on the scan vendors setting but it seems to have some kind of interference with the Vapor Core/Octane handler.
Let me know if you have a solution or if I can produce further information.
Cheers π»
OS: darwin Invoker Version: 2.9.0 Laravel Version: 9.18.0 Local project: true PHP Binary: /usr/local/bin/php Route: /home
Error: