0.3.0 generate migrations path

Issue Description

Expected Behavior

When running migration:generate, I expect the migration generated goes into the migrations path set in the parameter of the DataSource constructor.

Basically, I expect it to generate a migration into the path: E:\Projects\Discord Bots\commissions\luigical\src\migrations\<the_migration_file_here>.ts

Actual Behavior

Generating and creating migrations works but it goes into project root folder.

$ yarn typeorm:generate CreateGuildTable
yarn run v1.22.17
$ yarn typeorm:cli migration:generate -d src/ormconfig.ts CreateGuildTable
$ ts-node ./node_modules/typeorm/cli.js migration:generate -d src/ormconfig.ts CreateGuildTable
Migration E:\Projects\Discord Bots\commissions\luigical\CreateGuildTable.ts has been generated successfully.
Done in 9.21s.

Steps to Reproduce

1. Use the code below
2. Create an entity schema in the path project\src\entities\table-name.entity.ts
3. Run the migration:generate command - in my case the scripts I used are:

"typeorm:cli": "ts-node ./node_modules/typeorm/cli.js",
"typeorm:generate": "yarn typeorm:cli migration:generate -d src/ormconfig.ts",

1. It does not generate the migration in the correct path

const config: DataSourceOptions = {
  type: 'mysql',
  host: process.env.MYSQL_HOST,
  port: Number(process.env.MYSQL_PORT) || 3306,
  username: process.env.MYSQL_USERNAME,
  password: process.env.MYSQL_PASSWORD,
  database: process.env.MYSQL_DATABASE_NAME,
  entities: [__dirname + '\\entities\\**\\*{.ts,.js}'],
  migrations: [__dirname + '\\migrations\\**\\*{.ts,.js}'],
  cli: {
    migrationsDir: 'src\\migrations',
    entitiesDir: 'src\\entities'
  },
  synchronize: false
};

export const dataSource = new DataSource(config);

My Environment

Dependency	Version
Operating System	Windows 10 Home
Node.js version	17.3.0
Typescript version	4.5.5
TypeORM version	0.3.0

Additional Context

Relevant Database Driver(s)

DB Type	Reproducible
aurora-mysql	no
aurora-postgres	no
better-sqlite3	no
cockroachdb	no
cordova	no
expo	no
mongodb	no
mysql	yes
nativescript	no
oracle	no
postgres	no
react-native	no
sap	no
sqlite	no
sqlite-abstract	no
sqljs	no
sqlserver	no

Are you willing to resolve this issue by submitting a Pull Request?

• ✖️ Yes, I have the time, and I know how to start.
• ✖️ Yes, I have the time, but I don’t know how to start. I would need guidance.
• ✖️ No, I don’t have the time, but I can support (using donations) development.
• ✅ No, I don’t have the time and I’m okay to wait for the community / maintainers to resolve this issue.

[ryanoboril]

You need to specify full path now.

@pleerock absolutely ridiculous change

[cyril-git-h]

You need to specify full path now

what the hell? it’s exhausting and not convenient at all. How to configure path once? you should’ve thought about it. And please update documentation, it’s confusing.