How to structure a Symfony project according to the package-by-feature principle?

Question

PHP

Greetings.

I want to try to make the structure of a new application and I want to try the package-by-feature folder organization approach.

Where to store Kernel.php, what to do with migrations and tests. But in general, I want to look at something already implemented.

Can someone give examples of a Symphony project structure based on the package-by-feature principle?

So far I've settled on this structure:

.docker/
bin/
config/
migrations/
public/
src/
    Kernel.php
    API/
        Yandex/
        WebMoney/
    Cart/
        Console/
            UpdateCartCommand.php
        Controller/
            CartController.php
        Entity/
             Cart.php
        Repository/
            CartRepository.php
    Infrastructure/  
    Order/
        Console/
        Controller/
        Entity/
        Repository/
templates/
tests/
translations/
var/
vendor/

Answer 1

Architecture has nothing to do with the framework at all.
From the examples, I can advise an example of Dmitry Eliseev's project on slim . And there is also a report from Valentin Udaltsov about the architecture on Symfony.
1. Store the kernel in srcif it is one.
2. Migrations are possible src/Data/MigrationOr src/Migration
3. Tests, if common (functional), then to /tests, and if unit, then to the folder where the feature is. src/Feature/Test
From your structure, I would put Console and Controllers into one folder at the level with Feature.
Also, I would not do all-in-one services either services.yaml, but I would take them out in config/services/feature.yamlOr in each feature.