Error: Target class . . .

cgu2022

Hi! Thanks for clicking on this discussion!!

The issue

I've built an extension where every discussion page has a button that allows you to generate a summary of the entire conversation (the everyone's posts for that page) via OpenAI's API. My GitHub link is here.

The local version of my extension works through the local "packages" folder and added to composer.json via this command:

composer require cgu2022/flarum-hello-world *@dev

However, with the published version of my extension (without the "*@dev" command), when I click on the generate summary button, I get this error:

Next Illuminate\Contracts\Container\BindingResolutionException: Target class [CGU2022\CS278Extension\Api\GenerateSummaryController] does not exist. in C:\Projects\cs278-flarum\vendor\illuminate\container\Container.php:879 Stack trace: #0 C:\Projects\cs278-flarum\vendor\illuminate\container\Container.php(758): Illuminate\Container\Container->build() #1 C:\Projects\cs278-flarum\vendor\illuminate\container\Container.php(694): Illuminate\Container\Container->resolve()
. . .

and I've verified my file structure is what I intended, I would imagine it's correct since my extension works locally. I've also tried "composer dump-autoload," but it doesn't help.

Anyone encountered a similar error like this before or have any insights?

luceos

cgu2022 CGU2022\CS278Extension\Api\GenerateSummaryController

Your psr-4 instruction in composer.json says that:

CGU2022\\CS278Extension is mapped to src/, as a consequence Api\GenerateSummaryController will be searched for exactly in the directory Api/GenerateSummaryController. Your folder is named api though.

Now on systems that have disks that are case insensitive, like Windows and Apple devices, you will not likely encounter an error (though it is still wrong). Linux systems will blatantly call you out on your mistake though.

PS every developer encounters this problem at some point, some sooner than later. Working on Windows systems with case insensitive disks will make it harder to spot this issue early. If you work on windows, using WSL with a linux system like ubuntu helps you with this, but also makes managing your webserver harder.

cgu2022

luceos Luceos, thanks so much for your help!! Yes, it was indeed the case sensitivity issue. Apparently, GitHub is case-insensitive by default when making commits. For example, I first pushed a commit with "api." However, when I change the folder name to "Api" locally, GitHub will not keep track of the letter capitalization change. To have GitHub do this, you'll need to run this command, which is what I did to resolve the problem:

git config core.ignorecase false

Thank you also for the information about case sensitivity on OSes! I'll definitely keep that in mind moving forward as a developer 🙂