Recommendations? Composer psr-4 skipping yml files about eventsauce HOT 20 CLOSED

(I ran composer du)

from eventsauce.

@sandervanhooft have your tried classmap?

from eventsauce.

yes, no luck there either yet. Not completely sure yet what I should put in there in this case tbh

from eventsauce.

Hang on, I think you're right

from eventsauce.

I've just created a bunch of random classes in a file and required it using the autoload.files, and I can autoload them just fine on composer 2.0.11.

from eventsauce.

autoload.classmap seems to do the trick here

autoload.files doesn't somehow

from eventsauce.

(also on composer 2.0.11 here)

from eventsauce.

That's weird, the autoload.files should just always be loaded. There shouldn't be any difference between composer 1 and 2 here since it's always used for loading functions... very strange

from eventsauce.

So this works:

"autoload": {
        "classmap": [
            "src/Domain/SomeModule/commands_and_events.php"
        ],
        "psr-4": {
            "App\\": "src/App/",
            "Database\\Factories\\": "database/factories/",
            "Database\\Seeders\\": "database/seeders/",
            "Domain\\": "src/Domain/",
            "Support\\": "src/Support/"
        }
    },

from eventsauce.

Note that src/Domain is also used in autoload.psr-4, looks to me as if the autoload.psr-4 runs after the autoload.files and then decides to skip/remove the files (edit)

from eventsauce.

So it may be a composer autoloader hierarchy issue

from eventsauce.

{
    "name": "test/something",
    "autoload": {
        "psr-4": {
            "Domain\\": "src/Domain"
        },
        "files": [
            "src/Domain/classes.php"
        ]
    },
    "require": {
        "eventsauce/eventsauce": "^0.8.2"
    }
}

this works for me

from eventsauce.

Still getting the same warnings / skips here... Even after a complete reinstall

rm -rf composer.lock vendor && composer update

from eventsauce.

@sandervanhooft can you share an example repo with me where you experience this issue?

from eventsauce.

It's solved when using the classmap

from eventsauce.

Let me see if I can whip something up for you

from eventsauce.

Here you go:

https://github.com/sandervanhooft/es_composer_issue

from eventsauce.

It's using the Laravel wrapper, I don't expect that will be the cause.

Here's my output

from eventsauce.

@sandervanhooft ah now I understand what you meant. Then yeah, this is expected behaviour and the class-map is the solution. Your issue didn't specify during which operation it skipped the files and it seems your installation is configured to optimise the autoloader always (https://github.com/sandervanhooft/es_composer_issue/blob/main/composer.json#L28), so when I dumped it didn't give me this message. I then assumed you meant it skipped it when trying to load it. Which is then of course not the case. Mystery solved for me at least. Then the answer is relatively simple, use class-map :)

from eventsauce.

"optimize-autoloader": true,

Oh my that's a nifty little bugger.

That's standard Laravel boilerplate. Good to be aware of this. Thanks!

from eventsauce.