Not using mod.rs as the entry point of the generated entities

[nyc4m]

Hey there 👋

When generating entities, I noticed that the output code is using the "old" convention for modules, which is to output the source files as the following:

sea-orm-cli generate entity --database-url <DB_URL> --output-dir ./src/entities

# Resulting module structure
./src/entities
    /entities
        mod.rs
        foo.rs
        bar.rs
        prelude.rs

I'd rather use the "new" convention as described here. This would result in the following file structure:

sea-orm-cli generate entity --database-url <DB_URL> --output-dir ./src/entities

# Resulting module structure
./src/entities/
    entities.rs
    entities/
        foo.rs
        bar.rs
        prelude.rs

Is there anyway I can achieve this with the current CLI ?

[raffomania]

I've noticed that the migrate generate command also doesn't seem to work with the new module naming convention:

sea-orm-cli migrate generate --migration-dir src/bin/backend/db/migrations init
Generating new migration...
Creating migration file `src/bin/backend/db/migrations/m20250811_161046_init.rs`
Adding migration `m20250811_161046_init` to `src/bin/backend/db/migrations/mod.rs`
No such file or directory (os error 2)

The migration file is still generated, but the error is confusing nonetheless.

[Huliiiiii]

Converted to issue #2690.