-
Notifications
You must be signed in to change notification settings - Fork 0
Analyze crashes on trying to create app’s presenter #3
Comments
I think the search config is hooking to your project and tries to load your appDir parameter. How does it change, when you register services manually in barista config? |
It is the same error when I drop the |
I actually got a different error. I saw that one before as well. |
Something fishy is in place. I deleted the presenters and run
|
$ vendor/bin/barista list
[...]
Available commands:
completion Dump the shell completion script
help Display help for a command
lint Lint your Latte files with your own Latte\Engine. Provide it via "barista.neon" > "parameters" > "latteProviderFile" parameter
list List commands /me pulling hair |
I'd be really interested in reproducer for this original one :) Uncaught Nette\DI\ServiceCreationException: Service 'application.1' (t |
Right. Since trying it in nette sandbox just gave me a different error message, I am trying to simplify my project by deleting files left and right. Only to get more and more bizarre errors. I should probably step away from PHP for today. |
Yea, take your time and relax. Debugging can suck out of live very quickly, keep healthy 🍺 |
I tried to add more own dependency services, but it did not help to crash :/ The search extension works really poorly. I wish it allowed PHP syntax so we can use normal absolute path. This is my random guess: |
As mentioned, it does happen when I remove the Edit: Right, still the same at a0455c3. |
The distinguishing factor is actually classmap autoload in composer.json.
After trying almost every possible subset of files to delete from the project, it turned out that I have decided to port the legacy app to PSR-4 (unfortunately, Rector\PSR4\Rector\FileWithoutNamespace\NormalizeNamespaceByPSR4ComposerAutoloadRector is insufficient). Not sure if this is worth debugging further. |
Running
vendor/bin/barista analyze
in my Nette project using 08fa2df crashes with the following error:Initially reported in #2.
The text was updated successfully, but these errors were encountered: