Remove ConnectionManager test suite

• Entire test file removed (259 lines deleted)
• Contained tests for ConnectionManager.create() and ConnectionManager.get() methods
• Tested connection creation with MySQL driver and error handling

test/functional/connection-manager/connection-manager.test.ts

Update MongoDB docs to use DataSource

• Removed import statement for deprecated getMongoManager function
• Updated code example to use dataSource.mongoManager instead
• Changed from global function call to DataSource property access

docs/docs/drivers/mongodb.md

Document removed APIs in v1 migration guide

• Added new section documenting removed global convenience functions
• Listed all 11 removed functions with their replacements
• Provided before/after code examples showing migration path
• Added section documenting ConnectionManager removal

docs/docs/guides/8-migration-v1.md

Update query builder docs to use DataSource

• Updated 8 code examples to use dataSource.createQueryBuilder() instead of global
 createQueryBuilder()
• Changed from standalone function calls to DataSource method calls
• Maintained all query builder functionality and logic

docs/docs/query-builder/1-select-query-builder.md

Description

The v1 migration guide suggests const qb = dataSource.createQueryBuilder("user"), which is not a
valid DataSource.createQueryBuilder usage. This will fail TypeScript type-checking and does not
establish the main alias/from needed for a working query builder.

Code

docs/docs/guides/8-migration-v1.md[R138-139]

+const repo = dataSource.getRepository(User)
+const qb = dataSource.createQueryBuilder("user")

Evidence

The migration guide’s “After” snippet calls dataSource.createQueryBuilder("user") with one
argument, but DataSource.createQueryBuilder requires (entityClass, alias) to create a query
builder with a main alias; the 1-arg overload is for QueryRunner only.

docs/docs/guides/8-migration-v1.md[132-140]
src/data-source/DataSource.ts[547-586]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The migration guide instructs users to replace the removed global `createQueryBuilder("user")` with `dataSource.createQueryBuilder("user")`, which is not a valid overload for `DataSource.createQueryBuilder`.
### Issue Context
`DataSource.createQueryBuilder` requires `(entityClass, alias)` to create a query builder with a main alias (e.g., `"user"`). With one argument, it is the `queryRunner?: QueryRunner` overload.
### Fix Focus Areas
- docs/docs/guides/8-migration-v1.md[132-140]
- src/data-source/DataSource.ts[544-586]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The select query builder docs now show dataSource.createQueryBuilder("user"), but
DataSource.createQueryBuilder has no overload that accepts a single string alias; the 1-arg
overload is for QueryRunner, so this example is invalid/misleading.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
.leftJoinAndSelect("user.photos", "photo")

Evidence

DataSource.createQueryBuilder requires (entityClass, alias) when providing an alias. If alias
is omitted, the method treats the first parameter as a QueryRunner and constructs
SelectQueryBuilder with it, meaning a string like "user" is not a valid call. The same doc file
already demonstrates the correct pattern via
dataSource.getRepository(User).createQueryBuilder("user").

src/data-source/DataSource.ts[554-596]
docs/docs/query-builder/1-select-query-builder.md[11-16]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Docs now show `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string alias. This is an invalid example and will confuse users.
### Issue Context
`DataSource.createQueryBuilder` overloads are:
- `(entityClass, alias, queryRunner?)`
- `(queryRunner?)`
So alias-only calls must be via repository (`dataSource.getRepository(User).createQueryBuilder("user")`) or by providing the entity target (`dataSource.createQueryBuilder(User, "user")`).
### Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-809]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

Docs now use dataSource.createQueryBuilder("user"), but DataSource.createQueryBuilder requires
either (entity, alias) or a QueryRunner; a single string argument won’t type-check and can’t
produce the intended aliased query builder.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
.leftJoinAndSelect("user.photos", "photo")

Evidence

The documentation example calls dataSource.createQueryBuilder("user") with a single string
argument. In the actual API, DataSource.createQueryBuilder only overloads to `(entityClass, alias,
queryRunner?) or (queryRunner?); when no alias` is provided, the implementation treats the first
argument as a QueryRunner, so a string is not a valid usage for producing an aliased builder.

docs/docs/query-builder/1-select-query-builder.md[621-629]
src/data-source/DataSource.ts[544-586]
docs/docs/query-builder/1-select-query-builder.md[68-100]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs call `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string argument for creating an aliased query builder.
## Issue Context
`DataSource.createQueryBuilder` requires `(entityTarget, alias)` to build a query builder with `FROM`/`SELECT` preconfigured, or it takes a `QueryRunner` when called with a single argument.
## Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-626]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

MongoDB docs now use dataSource.mongoManager, but the page bootstraps myDataSource; the snippet
references an undefined identifier and will fail if copied.

Code

docs/docs/drivers/mongodb.md[R205-206]

+const manager = dataSource.mongoManager
await manager.save(user)

Evidence

The page defines the DataSource instance as myDataSource, but the updated example uses
dataSource.mongoManager without defining dataSource. This creates a copy/paste runtime failure
in documentation.

docs/docs/drivers/mongodb.md[117-126]
docs/docs/drivers/mongodb.md[192-206]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
MongoDB docs reference `dataSource.mongoManager` but only define `myDataSource`.
## Issue Context
After removing `getMongoManager()`, the example must access the manager via the actual `DataSource` instance variable used in the page.
## Fix Focus Areas
- docs/docs/drivers/mongodb.md[118-126]
- docs/docs/drivers/mongodb.md[205-206]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

Docs now use dataSource.createQueryBuilder("user"), but DataSource.createQueryBuilder requires
either (entity, alias) or a QueryRunner; a single string argument won’t type-check and can’t
produce the intended aliased query builder.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
  .leftJoinAndSelect("user.photos", "photo")

Evidence

The documentation example calls dataSource.createQueryBuilder("user") with a single string
argument. In the actual API, DataSource.createQueryBuilder only overloads to `(entityClass, alias,
queryRunner?) or (queryRunner?); when no alias` is provided, the implementation treats the first
argument as a QueryRunner, so a string is not a valid usage for producing an aliased builder.

docs/docs/query-builder/1-select-query-builder.md[621-629]
src/data-source/DataSource.ts[544-586]
docs/docs/query-builder/1-select-query-builder.md[68-100]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs call `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string argument for creating an aliased query builder.
## Issue Context
`DataSource.createQueryBuilder` requires `(entityTarget, alias)` to build a query builder with `FROM`/`SELECT` preconfigured, or it takes a `QueryRunner` when called with a single argument.
## Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-626]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

MongoDB docs now use dataSource.mongoManager, but the page bootstraps myDataSource; the snippet
references an undefined identifier and will fail if copied.

Code

docs/docs/drivers/mongodb.md[R205-206]

+const manager = dataSource.mongoManager
await manager.save(user)

Evidence

The page defines the DataSource instance as myDataSource, but the updated example uses
dataSource.mongoManager without defining dataSource. This creates a copy/paste runtime failure
in documentation.

docs/docs/drivers/mongodb.md[117-126]
docs/docs/drivers/mongodb.md[192-206]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
MongoDB docs reference `dataSource.mongoManager` but only define `myDataSource`.
## Issue Context
After removing `getMongoManager()`, the example must access the manager via the actual `DataSource` instance variable used in the page.
## Fix Focus Areas
- docs/docs/drivers/mongodb.md[118-126]
- docs/docs/drivers/mongodb.md[205-206]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The v1 migration guide suggests const qb = dataSource.createQueryBuilder("user"), which is not a
valid DataSource.createQueryBuilder usage. This will fail TypeScript type-checking and does not
establish the main alias/from needed for a working query builder.

Code

docs/docs/guides/8-migration-v1.md[R138-139]

+const repo = dataSource.getRepository(User)
+const qb = dataSource.createQueryBuilder("user")

Evidence

The migration guide’s “After” snippet calls dataSource.createQueryBuilder("user") with one
argument, but DataSource.createQueryBuilder requires (entityClass, alias) to create a query
builder with a main alias; the 1-arg overload is for QueryRunner only.

docs/docs/guides/8-migration-v1.md[132-140]
src/data-source/DataSource.ts[547-586]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The migration guide instructs users to replace the removed global `createQueryBuilder("user")` with `dataSource.createQueryBuilder("user")`, which is not a valid overload for `DataSource.createQueryBuilder`.
### Issue Context
`DataSource.createQueryBuilder` requires `(entityClass, alias)` to create a query builder with a main alias (e.g., `"user"`). With one argument, it is the `queryRunner?: QueryRunner` overload.
### Fix Focus Areas
- docs/docs/guides/8-migration-v1.md[132-140]
- src/data-source/DataSource.ts[544-586]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The select query builder docs now show dataSource.createQueryBuilder("user"), but
DataSource.createQueryBuilder has no overload that accepts a single string alias; the 1-arg
overload is for QueryRunner, so this example is invalid/misleading.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
 .leftJoinAndSelect("user.photos", "photo")

Evidence

DataSource.createQueryBuilder requires (entityClass, alias) when providing an alias. If alias
is omitted, the method treats the first parameter as a QueryRunner and constructs
SelectQueryBuilder with it, meaning a string like "user" is not a valid call. The same doc file
already demonstrates the correct pattern via
dataSource.getRepository(User).createQueryBuilder("user").

src/data-source/DataSource.ts[554-596]
docs/docs/query-builder/1-select-query-builder.md[11-16]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Docs now show `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string alias. This is an invalid example and will confuse users.
### Issue Context
`DataSource.createQueryBuilder` overloads are:
- `(entityClass, alias, queryRunner?)`
- `(queryRunner?)`
So alias-only calls must be via repository (`dataSource.getRepository(User).createQueryBuilder("user")`) or by providing the entity target (`dataSource.createQueryBuilder(User, "user")`).
### Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-809]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

Docs now use dataSource.createQueryBuilder("user"), but DataSource.createQueryBuilder requires
either (entity, alias) or a QueryRunner; a single string argument won’t type-check and can’t
produce the intended aliased query builder.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
 .leftJoinAndSelect("user.photos", "photo")

Evidence

The documentation example calls dataSource.createQueryBuilder("user") with a single string
argument. In the actual API, DataSource.createQueryBuilder only overloads to `(entityClass, alias,
queryRunner?) or (queryRunner?); when no alias` is provided, the implementation treats the first
argument as a QueryRunner, so a string is not a valid usage for producing an aliased builder.

docs/docs/query-builder/1-select-query-builder.md[621-629]
src/data-source/DataSource.ts[544-586]
docs/docs/query-builder/1-select-query-builder.md[68-100]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs call `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string argument for creating an aliased query builder.
## Issue Context
`DataSource.createQueryBuilder` requires `(entityTarget, alias)` to build a query builder with `FROM`/`SELECT` preconfigured, or it takes a `QueryRunner` when called with a single argument.
## Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-626]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

MongoDB docs now use dataSource.mongoManager, but the page bootstraps myDataSource; the snippet
references an undefined identifier and will fail if copied.

Code

docs/docs/drivers/mongodb.md[R205-206]

+const manager = dataSource.mongoManager
await manager.save(user)

Evidence

The page defines the DataSource instance as myDataSource, but the updated example uses
dataSource.mongoManager without defining dataSource. This creates a copy/paste runtime failure
in documentation.

docs/docs/drivers/mongodb.md[117-126]
docs/docs/drivers/mongodb.md[192-206]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
MongoDB docs reference `dataSource.mongoManager` but only define `myDataSource`.
## Issue Context
After removing `getMongoManager()`, the example must access the manager via the actual `DataSource` instance variable used in the page.
## Fix Focus Areas
- docs/docs/drivers/mongodb.md[118-126]
- docs/docs/drivers/mongodb.md[205-206]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The v1 migration guide’s removed-global-functions list does not include some globals stated as
removed in the PR (e.g., getMongoManager, getMongoRepository). This can mislead users upgrading
to v1 and leaves the breaking change incompletely documented.

Code

docs/docs/guides/8-migration-v1.md[R118-129]

+The following deprecated global functions have been removed:
+
+- `createConnection` / `createConnections`
+- `getConnection`
+- `getConnectionManager`
+- `getConnectionOptions`
+- `getManager`
+- `getSqljsManager`
+- `getRepository`
+- `getTreeRepository`
+- `createQueryBuilder`
+

Evidence

Compliance requires docs to reflect user-facing changes. The PR description lists additional removed
global functions, but the migration guide’s new “Global convenience functions” section omits at
least getMongoManager and getMongoRepository from the removed-functions list.

Rule 2: Docs updated for user-facing changes
docs/docs/guides/8-migration-v1.md[118-129]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The v1 migration guide section "Global convenience functions" lists removed globals, but it omits some functions the PR declares as removed (e.g., `getMongoManager`, `getMongoRepository`). This makes the breaking change documentation incomplete.
## Issue Context
The PR description explicitly enumerates the removed global functions; the migration guide should match that list (or clearly explain why some are documented elsewhere).
## Fix Focus Areas
- docs/docs/guides/8-migration-v1.md[116-145]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The select query builder docs now show dataSource.createQueryBuilder("user"), but
DataSource.createQueryBuilder has no overload that accepts a single string alias; the 1-arg
overload is for QueryRunner, so this example is invalid/misleading.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
.leftJoinAndSelect("user.photos", "photo")

Evidence

DataSource.createQueryBuilder requires (entityClass, alias) when providing an alias. If alias
is omitted, the method treats the first parameter as a QueryRunner and constructs
SelectQueryBuilder with it, meaning a string like "user" is not a valid call. The same doc file
already demonstrates the correct pattern via
dataSource.getRepository(User).createQueryBuilder("user").

src/data-source/DataSource.ts[554-596]
docs/docs/query-builder/1-select-query-builder.md[11-16]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Docs now show `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string alias. This is an invalid example and will confuse users.
### Issue Context
`DataSource.createQueryBuilder` overloads are:
- `(entityClass, alias, queryRunner?)`
- `(queryRunner?)`
So alias-only calls must be via repository (`dataSource.getRepository(User).createQueryBuilder("user")`) or by providing the entity target (`dataSource.createQueryBuilder(User, "user")`).
### Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-809]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

Docs now use dataSource.createQueryBuilder("user"), but DataSource.createQueryBuilder requires
either (entity, alias) or a QueryRunner; a single string argument won’t type-check and can’t
produce the intended aliased query builder.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
.leftJoinAndSelect("user.photos", "photo")

Evidence

The documentation example calls dataSource.createQueryBuilder("user") with a single string
argument. In the actual API, DataSource.createQueryBuilder only overloads to `(entityClass, alias,
queryRunner?) or (queryRunner?); when no alias` is provided, the implementation treats the first
argument as a QueryRunner, so a string is not a valid usage for producing an aliased builder.

docs/docs/query-builder/1-select-query-builder.md[621-629]
src/data-source/DataSource.ts[544-586]
docs/docs/query-builder/1-select-query-builder.md[68-100]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs call `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string argument for creating an aliased query builder.
## Issue Context
`DataSource.createQueryBuilder` requires `(entityTarget, alias)` to build a query builder with `FROM`/`SELECT` preconfigured, or it takes a `QueryRunner` when called with a single argument.
## Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-626]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

MongoDB docs now use dataSource.mongoManager, but the page bootstraps myDataSource; the snippet
references an undefined identifier and will fail if copied.

Code

docs/docs/drivers/mongodb.md[R205-206]

+const manager = dataSource.mongoManager
await manager.save(user)

Evidence

The page defines the DataSource instance as myDataSource, but the updated example uses
dataSource.mongoManager without defining dataSource. This creates a copy/paste runtime failure
in documentation.

docs/docs/drivers/mongodb.md[117-126]
docs/docs/drivers/mongodb.md[192-206]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
MongoDB docs reference `dataSource.mongoManager` but only define `myDataSource`.
## Issue Context
After removing `getMongoManager()`, the example must access the manager via the actual `DataSource` instance variable used in the page.
## Fix Focus Areas
- docs/docs/drivers/mongodb.md[118-126]
- docs/docs/drivers/mongodb.md[205-206]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The v1 migration guide suggests const qb = dataSource.createQueryBuilder("user"), which is not a
valid DataSource.createQueryBuilder usage. This will fail TypeScript type-checking and does not
establish the main alias/from needed for a working query builder.

Code

docs/docs/guides/8-migration-v1.md[R138-139]

+const repo = dataSource.getRepository(User)
+const qb = dataSource.createQueryBuilder("user")

Evidence

The migration guide’s “After” snippet calls dataSource.createQueryBuilder("user") with one
argument, but DataSource.createQueryBuilder requires (entityClass, alias) to create a query
builder with a main alias; the 1-arg overload is for QueryRunner only.

docs/docs/guides/8-migration-v1.md[132-140]
src/data-source/DataSource.ts[547-586]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The migration guide instructs users to replace the removed global `createQueryBuilder("user")` with `dataSource.createQueryBuilder("user")`, which is not a valid overload for `DataSource.createQueryBuilder`.
### Issue Context
`DataSource.createQueryBuilder` requires `(entityClass, alias)` to create a query builder with a main alias (e.g., `"user"`). With one argument, it is the `queryRunner?: QueryRunner` overload.
### Fix Focus Areas
- docs/docs/guides/8-migration-v1.md[132-140]
- src/data-source/DataSource.ts[544-586]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The select query builder docs now show dataSource.createQueryBuilder("user"), but
DataSource.createQueryBuilder has no overload that accepts a single string alias; the 1-arg
overload is for QueryRunner, so this example is invalid/misleading.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
.leftJoinAndSelect("user.photos", "photo")

Evidence

DataSource.createQueryBuilder requires (entityClass, alias) when providing an alias. If alias
is omitted, the method treats the first parameter as a QueryRunner and constructs
SelectQueryBuilder with it, meaning a string like "user" is not a valid call. The same doc file
already demonstrates the correct pattern via
dataSource.getRepository(User).createQueryBuilder("user").

src/data-source/DataSource.ts[554-596]
docs/docs/query-builder/1-select-query-builder.md[11-16]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Docs now show `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string alias. This is an invalid example and will confuse users.
### Issue Context
`DataSource.createQueryBuilder` overloads are:
- `(entityClass, alias, queryRunner?)`
- `(queryRunner?)`
So alias-only calls must be via repository (`dataSource.getRepository(User).createQueryBuilder("user")`) or by providing the entity target (`dataSource.createQueryBuilder(User, "user")`).
### Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-809]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

Docs now use dataSource.createQueryBuilder("user"), but DataSource.createQueryBuilder requires
either (entity, alias) or a QueryRunner; a single string argument won’t type-check and can’t
produce the intended aliased query builder.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
.leftJoinAndSelect("user.photos", "photo")

Evidence

The documentation example calls dataSource.createQueryBuilder("user") with a single string
argument. In the actual API, DataSource.createQueryBuilder only overloads to `(entityClass, alias,
queryRunner?) or (queryRunner?); when no alias` is provided, the implementation treats the first
argument as a QueryRunner, so a string is not a valid usage for producing an aliased builder.

docs/docs/query-builder/1-select-query-builder.md[621-629]
src/data-source/DataSource.ts[544-586]
docs/docs/query-builder/1-select-query-builder.md[68-100]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs call `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string argument for creating an aliased query builder.
## Issue Context
`DataSource.createQueryBuilder` requires `(entityTarget, alias)` to build a query builder with `FROM`/`SELECT` preconfigured, or it takes a `QueryRunner` when called with a single argument.
## Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-626]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

MongoDB docs now use dataSource.mongoManager, but the page bootstraps myDataSource; the snippet
references an undefined identifier and will fail if copied.

Code

docs/docs/drivers/mongodb.md[R205-206]

+const manager = dataSource.mongoManager
await manager.save(user)

Evidence

The page defines the DataSource instance as myDataSource, but the updated example uses
dataSource.mongoManager without defining dataSource. This creates a copy/paste runtime failure
in documentation.

docs/docs/drivers/mongodb.md[117-126]
docs/docs/drivers/mongodb.md[192-206]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
MongoDB docs reference `dataSource.mongoManager` but only define `myDataSource`.
## Issue Context
After removing `getMongoManager()`, the example must access the manager via the actual `DataSource` instance variable used in the page.
## Fix Focus Areas
- docs/docs/drivers/mongodb.md[118-126]
- docs/docs/drivers/mongodb.md[205-206]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

Docs now use dataSource.createQueryBuilder("user"), but DataSource.createQueryBuilder requires
either (entity, alias) or a QueryRunner; a single string argument won’t type-check and can’t
produce the intended aliased query builder.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
 .leftJoinAndSelect("user.photos", "photo")

Evidence

The documentation example calls dataSource.createQueryBuilder("user") with a single string
argument. In the actual API, DataSource.createQueryBuilder only overloads to `(entityClass, alias,
queryRunner?) or (queryRunner?); when no alias` is provided, the implementation treats the first
argument as a QueryRunner, so a string is not a valid usage for producing an aliased builder.

docs/docs/query-builder/1-select-query-builder.md[621-629]
src/data-source/DataSource.ts[544-586]
docs/docs/query-builder/1-select-query-builder.md[68-100]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs call `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string argument for creating an aliased query builder.
## Issue Context
`DataSource.createQueryBuilder` requires `(entityTarget, alias)` to build a query builder with `FROM`/`SELECT` preconfigured, or it takes a `QueryRunner` when called with a single argument.
## Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-626]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

MongoDB docs now use dataSource.mongoManager, but the page bootstraps myDataSource; the snippet
references an undefined identifier and will fail if copied.

Code

docs/docs/drivers/mongodb.md[R205-206]

+const manager = dataSource.mongoManager
await manager.save(user)

Evidence

The page defines the DataSource instance as myDataSource, but the updated example uses
dataSource.mongoManager without defining dataSource. This creates a copy/paste runtime failure
in documentation.

docs/docs/drivers/mongodb.md[117-126]
docs/docs/drivers/mongodb.md[192-206]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
MongoDB docs reference `dataSource.mongoManager` but only define `myDataSource`.
## Issue Context
After removing `getMongoManager()`, the example must access the manager via the actual `DataSource` instance variable used in the page.
## Fix Focus Areas
- docs/docs/drivers/mongodb.md[118-126]
- docs/docs/drivers/mongodb.md[205-206]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The v1 migration guide suggests const qb = dataSource.createQueryBuilder("user"), which is not a
valid DataSource.createQueryBuilder usage. This will fail TypeScript type-checking and does not
establish the main alias/from needed for a working query builder.

Code

docs/docs/guides/8-migration-v1.md[R138-139]

+const repo = dataSource.getRepository(User)
+const qb = dataSource.createQueryBuilder("user")

Evidence

The migration guide’s “After” snippet calls dataSource.createQueryBuilder("user") with one
argument, but DataSource.createQueryBuilder requires (entityClass, alias) to create a query
builder with a main alias; the 1-arg overload is for QueryRunner only.

docs/docs/guides/8-migration-v1.md[132-140]
src/data-source/DataSource.ts[547-586]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The migration guide instructs users to replace the removed global `createQueryBuilder("user")` with `dataSource.createQueryBuilder("user")`, which is not a valid overload for `DataSource.createQueryBuilder`.
### Issue Context
`DataSource.createQueryBuilder` requires `(entityClass, alias)` to create a query builder with a main alias (e.g., `"user"`). With one argument, it is the `queryRunner?: QueryRunner` overload.
### Fix Focus Areas
- docs/docs/guides/8-migration-v1.md[132-140]
- src/data-source/DataSource.ts[544-586]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

Docs now use dataSource.createQueryBuilder("user"), but DataSource.createQueryBuilder requires
either (entity, alias) or a QueryRunner; a single string argument won’t type-check and can’t
produce the intended aliased query builder.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
   .leftJoinAndSelect("user.photos", "photo")

Evidence

The documentation example calls dataSource.createQueryBuilder("user") with a single string
argument. In the actual API, DataSource.createQueryBuilder only overloads to `(entityClass, alias,
queryRunner?) or (queryRunner?); when no alias` is provided, the implementation treats the first
argument as a QueryRunner, so a string is not a valid usage for producing an aliased builder.

docs/docs/query-builder/1-select-query-builder.md[621-629]
[src/data-source/DataSource.ts[544-586]](https://github.com/t...

Description

MongoDB docs now use dataSource.mongoManager, but the page bootstraps myDataSource; the snippet
references an undefined identifier and will fail if copied.

Code

docs/docs/drivers/mongodb.md[R205-206]

+const manager = dataSource.mongoManager
await manager.save(user)

Evidence

The page defines the DataSource instance as myDataSource, but the updated example uses
dataSource.mongoManager without defining dataSource. This creates a copy/paste runtime failure
in documentation.

docs/docs/drivers/mongodb.md[117-126]
docs/docs/drivers/mongodb.md[192-206]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
MongoDB docs reference `dataSource.mongoManager` but only define `myDataSource`.
## Issue Context
After removing `getMongoManager()`, the example must access the manager via the actual `DataSource` instance variable used in the page.
## Fix Focus Areas
- docs/docs/drivers/mongodb.md[118-126]
- docs/docs/drivers/mongodb.md[205-206]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

MongoDB docs now use dataSource.mongoManager, but the page bootstraps myDataSource; the snippet
references an undefined identifier and will fail if copied.

Code

docs/docs/drivers/mongodb.md[R205-206]

+const manager = dataSource.mongoManager
await manager.save(user)

Evidence

The page defines the DataSource instance as myDataSource, but the updated example uses
dataSource.mongoManager without defining dataSource. This creates a copy/paste runtime failure
in documentation.

docs/docs/drivers/mongodb.md[117-126]
docs/docs/drivers/mongodb.md[192-206]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
MongoDB docs reference `dataSource.mongoManager` but only define `myDataSource`.
## Issue Context
After removing `getMongoManager()`, the example must access the manager via the actual `DataSource` instance variable used in the page.
## Fix Focus Areas
- docs/docs/drivers/mongodb.md[118-126]
- docs/docs/drivers/mongodb.md[205-206]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The v1 migration guide suggests const qb = dataSource.createQueryBuilder("user"), which is not a
valid DataSource.createQueryBuilder usage. This will fail TypeScript type-checking and does not
establish the main alias/from needed for a working query builder.

Code

docs/docs/guides/8-migration-v1.md[R138-139]

+const repo = dataSource.getRepository(User)
+const qb = dataSource.createQueryBuilder("user")

Evidence

The migration guide’s “After” snippet calls dataSource.createQueryBuilder("user") with one
argument, but DataSource.createQueryBuilder requires (entityClass, alias) to create a query
builder with a main alias; the 1-arg overload is for QueryRunner only.

docs/docs/guides/8-migration-v1.md[132-140]
src/data-source/DataSource.ts[547-586]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The migration guide instructs users to replace the removed global `createQueryBuilder("user")` with `dataSource.createQueryBuilder("user")`, which is not a valid overload for `DataSource.createQueryBuilder`.
### Issue Context
`DataSource.createQueryBuilder` requires `(entityClass, alias)` to create a query builder with a main alias (e.g., `"user"`). With one argument, it is the `queryRunner?: QueryRunner` overload.
### Fix Focus Areas
- docs/docs/guides/8-migration-v1.md[132-140]
- src/data-source/DataSource.ts[544-586]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The select query builder docs now show dataSource.createQueryBuilder("user"), but
DataSource.createQueryBuilder has no overload that accepts a single string alias; the 1-arg
overload is for QueryRunner, so this example is invalid/misleading.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
 .leftJoinAndSelect("user.photos", "photo")

Evidence

DataSource.createQueryBuilder requires (entityClass, alias) when providing an alias. If alias
is omitted, the method treats the first parameter as a QueryRunner and constructs
SelectQueryBuilder with it, meaning a string like "user" is not a valid call. The same doc file
already demonstrates the correct pattern via
dataSource.getRepository(User).createQueryBuilder("user").

src/data-source/DataSource.ts[554-596]
docs/docs/query-builder/1-select-query-builder.md[11-16]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Docs now show `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string alias. This is an invalid example and will confuse users.
### Issue Context
`DataSource.createQueryBuilder` overloads are:
- `(entityClass, alias, queryRunner?)`
- `(queryRunner?)`
So alias-only calls must be via repository (`dataSource.getRepository(User).createQueryBuilder("user")`) or by providing the entity target (`dataSource.createQueryBuilder(User, "user")`).
### Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-809]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

Docs now use dataSource.createQueryBuilder("user"), but DataSource.createQueryBuilder requires
either (entity, alias) or a QueryRunner; a single string argument won’t type-check and can’t
produce the intended aliased query builder.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
 .leftJoinAndSelect("user.photos", "photo")

Evidence

The documentation example calls dataSource.createQueryBuilder("user") with a single string
argument. In the actual API, DataSource.createQueryBuilder only overloads to `(entityClass, alias,
queryRunner?) or (queryRunner?); when no alias` is provided, the implementation treats the first
argument as a QueryRunner, so a string is not a valid usage for producing an aliased builder.

docs/docs/query-builder/1-select-query-builder.md[621-629]
src/data-source/DataSource.ts[544-586]
docs/docs/query-builder/1-select-query-builder.md[68-100]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs call `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string argument for creating an aliased query builder.
## Issue Context
`DataSource.createQueryBuilder` requires `(entityTarget, alias)` to build a query builder with `FROM`/`SELECT` preconfigured, or it takes a `QueryRunner` when called with a single argument.
## Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-626]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

MongoDB docs now use dataSource.mongoManager, but the page bootstraps myDataSource; the snippet
references an undefined identifier and will fail if copied.

Code

docs/docs/drivers/mongodb.md[R205-206]

+const manager = dataSource.mongoManager
await manager.save(user)

Evidence

The page defines the DataSource instance as myDataSource, but the updated example uses
dataSource.mongoManager without defining dataSource. This creates a copy/paste runtime failure
in documentation.

docs/docs/drivers/mongodb.md[117-126]
docs/docs/drivers/mongodb.md[192-206]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
MongoDB docs reference `dataSource.mongoManager` but only define `myDataSource`.
## Issue Context
After removing `getMongoManager()`, the example must access the manager via the actual `DataSource` instance variable used in the page.
## Fix Focus Areas
- docs/docs/drivers/mongodb.md[118-126]
- docs/docs/drivers/mongodb.md[205-206]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

Docs now use dataSource.createQueryBuilder("user"), but DataSource.createQueryBuilder requires
either (entity, alias) or a QueryRunner; a single string argument won’t type-check and can’t
produce the intended aliased query builder.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
   .leftJoinAndSelect("user.photos", "photo")

Evidence

The documentation example calls dataSource.createQueryBuilder("user") with a single string
argument. In the actual API, DataSource.createQueryBuilder only overloads to `(entityClass, alias,
queryRunner?) or (queryRunner?); when no alias` is provided, the implementation treats the first
argument as a QueryRunner, so a string is not a valid usage for producing an aliased builder.

docs/docs/query-builder/1-select-query-builder.md[621-629]
src/data-source/DataSource.ts[544-586]
docs/docs/query-builder/1-select-query-builder.md[68-100]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs call `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string argument for creating an aliased query builder.
## Issue Context
`DataSource.createQueryBuilder` requires `(entityTarget, alias)` to build a query builder with `FROM`/`SELECT` preconfigured, or it takes a `QueryRunner` when called with a single argument.
## Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-626]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

MongoDB docs now use dataSource.mongoManager, but the page bootstraps myDataSource; the snippet
references an undefined identifier and will fail if copied.

Code

docs/docs/drivers/mongodb.md[R205-206]

+const manager = dataSource.mongoManager
await manager.save(user)

Evidence

The page defines the DataSource instance as myDataSource, but the updated example uses
dataSource.mongoManager without defining dataSource. This creates a copy/paste runtime failure
in documentation.

docs/docs/drivers/mongodb.md[117-126]
docs/docs/drivers/mongodb.md[192-206]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
MongoDB docs reference `dataSource.mongoManager` but only define `myDataSource`.
## Issue Context
After removing `getMongoManager()`, the example must access the manager via the actual `DataSource` instance variable used in the page.
## Fix Focus Areas
- docs/docs/drivers/mongodb.md[118-126]
- docs/docs/drivers/mongodb.md[205-206]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The v1 migration guide suggests const qb = dataSource.createQueryBuilder("user"), which is not a
valid DataSource.createQueryBuilder usage. This will fail TypeScript type-checking and does not
establish the main alias/from needed for a working query builder.

Code

docs/docs/guides/8-migration-v1.md[R138-139]

+const repo = dataSource.getRepository(User)
+const qb = dataSource.createQueryBuilder("user")

Evidence

The migration guide’s “After” snippet calls dataSource.createQueryBuilder("user") with one
argument, but DataSource.createQueryBuilder requires (entityClass, alias) to create a query
builder with a main alias; the 1-arg overload is for QueryRunner only.

docs/docs/guides/8-migration-v1.md[132-140]
src/data-source/DataSource.ts[547-586]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The migration guide instructs users to replace the removed global `createQueryBuilder("user")` with `dataSource.createQueryBuilder("user")`, which is not a valid overload for `DataSource.createQueryBuilder`.
### Issue Context
`DataSource.createQueryBuilder` requires `(entityClass, alias)` to create a query builder with a main alias (e.g., `"user"`). With one argument, it is the `queryRunner?: QueryRunner` overload.
### Fix Focus Areas
- docs/docs/guides/8-migration-v1.md[132-140]
- src/data-source/DataSource.ts[544-586]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The select query builder docs now show dataSource.createQueryBuilder("user"), but
DataSource.createQueryBuilder has no overload that accepts a single string alias; the 1-arg
overload is for QueryRunner, so this example is invalid/misleading.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
  .leftJoinAndSelect("user.photos", "photo")

Evidence

DataSource.createQueryBuilder requires (entityClass, alias) when providing an alias. If alias
is omitted, the method treats the first parameter as a QueryRunner and constructs
SelectQueryBuilder with it, meaning a string like "user" is not a valid call. The same doc file
already demonstrates the correct pattern via
dataSource.getRepository(User).createQueryBuilder("user").

src/data-source/DataSource.ts[554-596]
docs/docs/query-builder/1-select-query-builder.md[11-16]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Docs now show `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string alias. This is an invalid example and will confuse users.
### Issue Context
`DataSource.createQueryBuilder` overloads are:
- `(entityClass, alias, queryRunner?)`
- `(queryRunner?)`
So alias-only calls must be via repository (`dataSource.getRepository(User).createQueryBuilder("user")`) or by providing the entity target (`dataSource.createQueryBuilder(User, "user")`).
### Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-809]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

Docs now use dataSource.createQueryBuilder("user"), but DataSource.createQueryBuilder requires
either (entity, alias) or a QueryRunner; a single string argument won’t type-check and can’t
produce the intended aliased query builder.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
  .leftJoinAndSelect("user.photos", "photo")

Evidence

The documentation example calls dataSource.createQueryBuilder("user") with a single string
argument. In the actual API, DataSource.createQueryBuilder only overloads to `(entityClass, alias,
queryRunner?) or (queryRunner?); when no alias` is provided, the implementation treats the first
argument as a QueryRunner, so a string is not a valid usage for producing an aliased builder.

docs/docs/query-builder/1-select-query-builder.md[621-629]
src/data-source/DataSource.ts[544-586]
docs/docs/query-builder/1-select-query-builder.md[68-100]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs call `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string argument for creating an aliased query builder.
## Issue Context
`DataSource.createQueryBuilder` requires `(entityTarget, alias)` to build a query builder with `FROM`/`SELECT` preconfigured, or it takes a `QueryRunner` when called with a single argument.
## Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-626]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

MongoDB docs now use dataSource.mongoManager, but the page bootstraps myDataSource; the snippet
references an undefined identifier and will fail if copied.

Code

docs/docs/drivers/mongodb.md[R205-206]

+const manager = dataSource.mongoManager
await manager.save(user)

Evidence

The page defines the DataSource instance as myDataSource, but the updated example uses
dataSource.mongoManager without defining dataSource. This creates a copy/paste runtime failure
in documentation.

docs/docs/drivers/mongodb.md[117-126]
docs/docs/drivers/mongodb.md[192-206]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
MongoDB docs reference `dataSource.mongoManager` but only define `myDataSource`.
## Issue Context
After removing `getMongoManager()`, the example must access the manager via the actual `DataSource` instance variable used in the page.
## Fix Focus Areas
- docs/docs/drivers/mongodb.md[118-126]
- docs/docs/drivers/mongodb.md[205-206]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The PR replaces an existing short comment with a much longer, numbered narrative block that reads
like generated filler and is inconsistent with the file’s prior concise style. This introduces
comment noise without changing behavior.

Code

src/globals.ts[R5-19]

+ * Returns the singleton MetadataArgsStorage, creating it on the global scope if it
+ * does not already exist.
*/
export function getMetadataArgsStorage(): MetadataArgsStorage {
-    // we should store metadata storage in a global variable otherwise it brings too much problems
-    // one of the problem is that if any entity (or any other) will be imported before consumer will call
-    // useContainer method with his own container implementation, that entity will be registered in the
-    // old old container (default one post probably) and consumer will his entity.
-    // calling useContainer before he imports any entity (or any other) is not always convenient.
-    // another reason is that when we run migrations typeorm is being called from a global package
-    // and it may load entities which register decorators in typeorm of local package
-    // this leads to impossibility of usage of entities in migrations and cli related operations
+    // We store the metadata storage in a global variable to avoid several problems:
+    //
+    // 1. If any entity (or other decorated class) is imported before the consumer calls
+    //    useContainer with a custom container implementation, that entity will be registered
+    //    in the old (default) container and the consumer will lose access to it. Requiring
+    //    useContainer to be called before importing any entity is not always convenient.
+    //
+    // 2. When running migrations, TypeORM may be invoked from a globally installed package
+    //    while loading entities that register decorators against a locally installed copy.
+    //    Without a shared global storage, entities become unavailable in migrations and
+    //    CLI-related operations.

Evidence

Compliance ID 4 requires avoiding AI-like comment noise and inconsistent style; the modified block
comment in src/globals.ts is significantly expanded into a verbose numbered explanation without
functional impact.

Rule 4: Remove AI-generated noise
src/globals.ts[5-19]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The updated comment block in `getMetadataArgsStorage()` is significantly more verbose than before and introduces stylistic/comment noise that may be perceived as AI-generated slop.
## Issue Context
Compliance requires avoiding extra/AI-like comments and inconsistent style. The change is purely comment-level (no behavior change), so it can be safely simplified.
## Fix Focus Areas
- src/globals.ts[5-19]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The PR replaces an existing short comment with a much longer, numbered narrative block that reads
like generated filler and is inconsistent with the file’s prior concise style. This introduces
comment noise without changing behavior.

Code

src/globals.ts[R5-19]

+ * Returns the singleton MetadataArgsStorage, creating it on the global scope if it
+ * does not already exist.
*/
export function getMetadataArgsStorage(): MetadataArgsStorage {
-    // we should store metadata storage in a global variable otherwise it brings too much problems
-    // one of the problem is that if any entity (or any other) will be imported before consumer will call
-    // useContainer method with his own container implementation, that entity will be registered in the
-    // old old container (default one post probably) and consumer will his entity.
-    // calling useContainer before he imports any entity (or any other) is not always convenient.
-    // another reason is that when we run migrations typeorm is being called from a global package
-    // and it may load entities which register decorators in typeorm of local package
-    // this leads to impossibility of usage of entities in migrations and cli related operations
+    // We store the metadata storage in a global variable to avoid several problems:
+    //
+    // 1. If any entity (or other decorated class) is imported before the consumer calls
+    //    useContainer with a custom container implementation, that entity will be registered
+    //    in the old (default) container and the consumer will lose access to it. Requiring
+    //    useContainer to be called before importing any entity is not always convenient.
+    //
+    // 2. When running migrations, TypeORM may be invoked from a globally installed package
+    //    while loading entities that register decorators against a locally installed copy.
+    //    Without a shared global storage, entities become unavailable in migrations and
+    //    CLI-related operations.

Evidence

Compliance ID 4 requires avoiding AI-like comment noise and inconsistent style; the modified block
comment in src/globals.ts is significantly expanded into a verbose numbered explanation without
functional impact.

Rule 4: Remove AI-generated noise
src/globals.ts[5-19]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The updated comment block in `getMetadataArgsStorage()` is significantly more verbose than before and introduces stylistic/comment noise that may be perceived as AI-generated slop.
## Issue Context
Compliance requires avoiding extra/AI-like comments and inconsistent style. The change is purely comment-level (no behavior change), so it can be safely simplified.
## Fix Focus Areas
- src/globals.ts[5-19]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

A large, newly added numbered comment block in getMetadataArgsStorage() reads like
AI-generated/excessively defensive explanation and may be considered noise. This conflicts with the
requirement to avoid extra comments and style inconsistencies in changes.

Code

src/globals.ts[R5-19]

+ * Returns the singleton MetadataArgsStorage, creating it on the global scope if it
+ * does not already exist.
*/
export function getMetadataArgsStorage(): MetadataArgsStorage {
-    // we should store metadata storage in a global variable otherwise it brings too much problems
-    // one of the problem is that if any entity (or any other) will be imported before consumer will call
-    // useContainer method with his own container implementation, that entity will be registered in the
-    // old old container (default one post probably) and consumer will his entity.
-    // calling useContainer before he imports any entity (or any other) is not always convenient.
-    // another reason is that when we run migrations typeorm is being called from a global package
-    // and it may load entities which register decorators in typeorm of local package
-    // this leads to impossibility of usage of entities in migrations and cli related operations
+    // We store the metadata storage in a global variable to avoid several problems:
+    //
+    // 1. If any entity (or other decorated class) is imported before the consumer calls
+    //    useContainer with a custom container implementation, that entity will be registered
+    //    in the old (default) container and the consumer will lose access to it. Requiring
+    //    useContainer to be called before importing any entity is not always convenient.
+    //
+    // 2. When running migrations, TypeORM may be invoked from a globally installed package
+    //    while loading entities that register decorators against a locally installed copy.
+    //    Without a shared global storage, entities become unavailable in migrations and
+    //    CLI-related operations.

Evidence

PR Compliance ID 4 requires avoiding AI-like slop such as unnecessary extra comments; the PR adds an
expanded, numbered rationale comment block in src/globals.ts as part of this change.

Rule 4: Remove AI-generated noise
src/globals.ts[5-19]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The PR adds an unusually long, numbered explanatory comment block in `getMetadataArgsStorage()` that may be considered AI-generated noise per the compliance checklist.
## Issue Context
Compliance requires avoiding extra comments and AI-like slop/style inconsistencies in changes.
## Fix Focus Areas
- src/globals.ts[5-19]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The PR replaces an existing short comment with a much longer, numbered narrative block that reads
like generated filler and is inconsistent with the file’s prior concise style. This introduces
comment noise without changing behavior.

Code

src/globals.ts[R5-19]

+ * Returns the singleton MetadataArgsStorage, creating it on the global scope if it
+ * does not already exist.
*/
export function getMetadataArgsStorage(): MetadataArgsStorage {
-    // we should store metadata storage in a global variable otherwise it brings too much problems
-    // one of the problem is that if any entity (or any other) will be imported before consumer will call
-    // useContainer method with his own container implementation, that entity will be registered in the
-    // old old container (default one post probably) and consumer will his entity.
-    // calling useContainer before he imports any entity (or any other) is not always convenient.
-    // another reason is that when we run migrations typeorm is being called from a global package
-    // and it may load entities which register decorators in typeorm of local package
-    // this leads to impossibility of usage of entities in migrations and cli related operations
+    // We store the metadata storage in a global variable to avoid several problems:
+    //
+    // 1. If any entity (or other decorated class) is imported before the consumer calls
+    //    useContainer with a custom container implementation, that entity will be registered
+    //    in the old (default) container and the consumer will lose access to it. Requiring
+    //    useContainer to be called before importing any entity is not always convenient.
+    //
+    // 2. When running migrations, TypeORM may be invoked from a globally installed package
+    //    while loading entities that register decorators against a locally installed copy.
+    //    Without a shared global storage, entities become unavailable in migrations and
+    //    CLI-related operations.

Evidence

Compliance ID 4 requires avoiding AI-like comment noise and inconsistent style; the modified block
comment in src/globals.ts is significantly expanded into a verbose numbered explanation without
functional impact.

Rule 4: Remove AI-generated noise
src/globals.ts[5-19]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The updated comment block in `getMetadataArgsStorage()` is significantly more verbose than before and introduces stylistic/comment noise that may be perceived as AI-generated slop.
## Issue Context
Compliance requires avoiding extra/AI-like comments and inconsistent style. The change is purely comment-level (no behavior change), so it can be safely simplified.
## Fix Focus Areas
- src/globals.ts[5-19]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

MongoDB docs now use dataSource.mongoManager, but the page bootstraps myDataSource; the snippet
references an undefined identifier and will fail if copied.

Code

docs/docs/drivers/mongodb.md[R205-206]

+const manager = dataSource.mongoManager
await manager.save(user)

Evidence

The page defines the DataSource instance as myDataSource, but the updated example uses
dataSource.mongoManager without defining dataSource. This creates a copy/paste runtime failure
in documentation.

docs/docs/drivers/mongodb.md[117-126]
docs/docs/drivers/mongodb.md[192-206]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
MongoDB docs reference `dataSource.mongoManager` but only define `myDataSource`.
## Issue Context
After removing `getMongoManager()`, the example must access the manager via the actual `DataSource` instance variable used in the page.
## Fix Focus Areas
- docs/docs/drivers/mongodb.md[118-126]
- docs/docs/drivers/mongodb.md[205-206]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The v1 migration guide suggests const qb = dataSource.createQueryBuilder("user"), which is not a
valid DataSource.createQueryBuilder usage. This will fail TypeScript type-checking and does not
establish the main alias/from needed for a working query builder.

Code

docs/docs/guides/8-migration-v1.md[R138-139]

+const repo = dataSource.getRepository(User)
+const qb = dataSource.createQueryBuilder("user")

Evidence

The migration guide’s “After” snippet calls dataSource.createQueryBuilder("user") with one
argument, but DataSource.createQueryBuilder requires (entityClass, alias) to create a query
builder with a main alias; the 1-arg overload is for QueryRunner only.

docs/docs/guides/8-migration-v1.md[132-140]
src/data-source/DataSource.ts[547-586]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The migration guide instructs users to replace the removed global `createQueryBuilder("user")` with `dataSource.createQueryBuilder("user")`, which is not a valid overload for `DataSource.createQueryBuilder`.
### Issue Context
`DataSource.createQueryBuilder` requires `(entityClass, alias)` to create a query builder with a main alias (e.g., `"user"`). With one argument, it is the `queryRunner?: QueryRunner` overload.
### Fix Focus Areas
- docs/docs/guides/8-migration-v1.md[132-140]
- src/data-source/DataSource.ts[544-586]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The select query builder docs now show dataSource.createQueryBuilder("user"), but
DataSource.createQueryBuilder has no overload that accepts a single string alias; the 1-arg
overload is for QueryRunner, so this example is invalid/misleading.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
.leftJoinAndSelect("user.photos", "photo")

Evidence

DataSource.createQueryBuilder requires (entityClass, alias) when providing an alias. If alias
is omitted, the method treats the first parameter as a QueryRunner and constructs
SelectQueryBuilder with it, meaning a string like "user" is not a valid call. The same doc file
already demonstrates the correct pattern via
dataSource.getRepository(User).createQueryBuilder("user").

src/data-source/DataSource.ts[554-596]
docs/docs/query-builder/1-select-query-builder.md[11-16]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Docs now show `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string alias. This is an invalid example and will confuse users.
### Issue Context
`DataSource.createQueryBuilder` overloads are:
- `(entityClass, alias, queryRunner?)`
- `(queryRunner?)`
So alias-only calls must be via repository (`dataSource.getRepository(User).createQueryBuilder("user")`) or by providing the entity target (`dataSource.createQueryBuilder(User, "user")`).
### Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-809]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

Docs now use dataSource.createQueryBuilder("user"), but DataSource.createQueryBuilder requires
either (entity, alias) or a QueryRunner; a single string argument won’t type-check and can’t
produce the intended aliased query builder.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
.leftJoinAndSelect("user.photos", "photo")

Evidence

The documentation example calls dataSource.createQueryBuilder("user") with a single string
argument. In the actual API, DataSource.createQueryBuilder only overloads to `(entityClass, alias,
queryRunner?) or (queryRunner?); when no alias` is provided, the implementation treats the first
argument as a QueryRunner, so a string is not a valid usage for producing an aliased builder.

docs/docs/query-builder/1-select-query-builder.md[621-629]
src/data-source/DataSource.ts[544-586]
docs/docs/query-builder/1-select-query-builder.md[68-100]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs call `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string argument for creating an aliased query builder.
## Issue Context
`DataSource.createQueryBuilder` requires `(entityTarget, alias)` to build a query builder with `FROM`/`SELECT` preconfigured, or it takes a `QueryRunner` when called with a single argument.
## Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-626]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

MongoDB docs now use dataSource.mongoManager, but the page bootstraps myDataSource; the snippet
references an undefined identifier and will fail if copied.

Code

docs/docs/drivers/mongodb.md[R205-206]

+const manager = dataSource.mongoManager
await manager.save(user)

Evidence

The page defines the DataSource instance as myDataSource, but the updated example uses
dataSource.mongoManager without defining dataSource. This creates a copy/paste runtime failure
in documentation.

docs/docs/drivers/mongodb.md[117-126]
docs/docs/drivers/mongodb.md[192-206]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
MongoDB docs reference `dataSource.mongoManager` but only define `myDataSource`.
## Issue Context
After removing `getMongoManager()`, the example must access the manager via the actual `DataSource` instance variable used in the page.
## Fix Focus Areas
- docs/docs/drivers/mongodb.md[118-126]
- docs/docs/drivers/mongodb.md[205-206]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

Docs now use dataSource.createQueryBuilder("user"), but DataSource.createQueryBuilder requires
either (entity, alias) or a QueryRunner; a single string argument won’t type-check and can’t
produce the intended aliased query builder.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
  .leftJoinAndSelect("user.photos", "photo")

Evidence

The documentation example calls dataSource.createQueryBuilder("user") with a single string
argument. In the actual API, DataSource.createQueryBuilder only overloads to `(entityClass, alias,
queryRunner?) or (queryRunner?); when no alias` is provided, the implementation treats the first
argument as a QueryRunner, so a string is not a valid usage for producing an aliased builder.

docs/docs/query-builder/1-select-query-builder.md[621-629]
src/data-source/DataSource.ts[544-586]
docs/docs/query-builder/1-select-query-builder.md[68-100]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs call `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string argument for creating an aliased query builder.
## Issue Context
`DataSource.createQueryBuilder` requires `(entityTarget, alias)` to build a query builder with `FROM`/`SELECT` preconfigured, or it takes a `QueryRunner` when called with a single argument.
## Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-626]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

MongoDB docs now use dataSource.mongoManager, but the page bootstraps myDataSource; the snippet
references an undefined identifier and will fail if copied.

Code

docs/docs/drivers/mongodb.md[R205-206]

+const manager = dataSource.mongoManager
await manager.save(user)

Evidence

The page defines the DataSource instance as myDataSource, but the updated example uses
dataSource.mongoManager without defining dataSource. This creates a copy/paste runtime failure
in documentation.

docs/docs/drivers/mongodb.md[117-126]
docs/docs/drivers/mongodb.md[192-206]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
MongoDB docs reference `dataSource.mongoManager` but only define `myDataSource`.
## Issue Context
After removing `getMongoManager()`, the example must access the manager via the actual `DataSource` instance variable used in the page.
## Fix Focus Areas
- docs/docs/drivers/mongodb.md[118-126]
- docs/docs/drivers/mongodb.md[205-206]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The v1 migration guide suggests const qb = dataSource.createQueryBuilder("user"), which is not a
valid DataSource.createQueryBuilder usage. This will fail TypeScript type-checking and does not
establish the main alias/from needed for a working query builder.

Code

docs/docs/guides/8-migration-v1.md[R138-139]

+const repo = dataSource.getRepository(User)
+const qb = dataSource.createQueryBuilder("user")

Evidence

The migration guide’s “After” snippet calls dataSource.createQueryBuilder("user") with one
argument, but DataSource.createQueryBuilder requires (entityClass, alias) to create a query
builder with a main alias; the 1-arg overload is for QueryRunner only.

docs/docs/guides/8-migration-v1.md[132-140]
src/data-source/DataSource.ts[547-586]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The migration guide instructs users to replace the removed global `createQueryBuilder("user")` with `dataSource.createQueryBuilder("user")`, which is not a valid overload for `DataSource.createQueryBuilder`.
### Issue Context
`DataSource.createQueryBuilder` requires `(entityClass, alias)` to create a query builder with a main alias (e.g., `"user"`). With one argument, it is the `queryRunner?: QueryRunner` overload.
### Fix Focus Areas
- docs/docs/guides/8-migration-v1.md[132-140]
- src/data-source/DataSource.ts[544-586]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The select query builder docs now show dataSource.createQueryBuilder("user"), but
DataSource.createQueryBuilder has no overload that accepts a single string alias; the 1-arg
overload is for QueryRunner, so this example is invalid/misleading.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
 .leftJoinAndSelect("user.photos", "photo")

Evidence

DataSource.createQueryBuilder requires (entityClass, alias) when providing an alias. If alias
is omitted, the method treats the first parameter as a QueryRunner and constructs
SelectQueryBuilder with it, meaning a string like "user" is not a valid call. The same doc file
already demonstrates the correct pattern via
dataSource.getRepository(User).createQueryBuilder("user").

src/data-source/DataSource.ts[554-596]
docs/docs/query-builder/1-select-query-builder.md[11-16]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Docs now show `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string alias. This is an invalid example and will confuse users.
### Issue Context
`DataSource.createQueryBuilder` overloads are:
- `(entityClass, alias, queryRunner?)`
- `(queryRunner?)`
So alias-only calls must be via repository (`dataSource.getRepository(User).createQueryBuilder("user")`) or by providing the entity target (`dataSource.createQueryBuilder(User, "user")`).
### Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-809]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

Docs now use dataSource.createQueryBuilder("user"), but DataSource.createQueryBuilder requires
either (entity, alias) or a QueryRunner; a single string argument won’t type-check and can’t
produce the intended aliased query builder.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
 .leftJoinAndSelect("user.photos", "photo")

Evidence

The documentation example calls dataSource.createQueryBuilder("user") with a single string
argument. In the actual API, DataSource.createQueryBuilder only overloads to `(entityClass, alias,
queryRunner?) or (queryRunner?); when no alias` is provided, the implementation treats the first
argument as a QueryRunner, so a string is not a valid usage for producing an aliased builder.

docs/docs/query-builder/1-select-query-builder.md[621-629]
src/data-source/DataSource.ts[544-586]
docs/docs/query-builder/1-select-query-builder.md[68-100]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs call `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string argument for creating an aliased query builder.
## Issue Context
`DataSource.createQueryBuilder` requires `(entityTarget, alias)` to build a query builder with `FROM`/`SELECT` preconfigured, or it takes a `QueryRunner` when called with a single argument.
## Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-626]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

MongoDB docs now use dataSource.mongoManager, but the page bootstraps myDataSource; the snippet
references an undefined identifier and will fail if copied.

Code

docs/docs/drivers/mongodb.md[R205-206]

+const manager = dataSource.mongoManager
await manager.save(user)

Evidence

The page defines the DataSource instance as myDataSource, but the updated example uses
dataSource.mongoManager without defining dataSource. This creates a copy/paste runtime failure
in documentation.

docs/docs/drivers/mongodb.md[117-126]
docs/docs/drivers/mongodb.md[192-206]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
MongoDB docs reference `dataSource.mongoManager` but only define `myDataSource`.
## Issue Context
After removing `getMongoManager()`, the example must access the manager via the actual `DataSource` instance variable used in the page.
## Fix Focus Areas
- docs/docs/drivers/mongodb.md[118-126]
- docs/docs/drivers/mongodb.md[205-206]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The v1 migration guide’s removed-global-functions list does not include some globals stated as
removed in the PR (e.g., getMongoManager, getMongoRepository). This can mislead users upgrading
to v1 and leaves the breaking change incompletely documented.

Code

docs/docs/guides/8-migration-v1.md[R118-129]

+The following deprecated global functions have been removed:
+
+- `createConnection` / `createConnections`
+- `getConnection`
+- `getConnectionManager`
+- `getConnectionOptions`
+- `getManager`
+- `getSqljsManager`
+- `getRepository`
+- `getTreeRepository`
+- `createQueryBuilder`
+

Evidence

Compliance requires docs to reflect user-facing changes. The PR description lists additional removed
global functions, but the migration guide’s new “Global convenience functions” section omits at
least getMongoManager and getMongoRepository from the removed-functions list.

Rule 2: Docs updated for user-facing changes
docs/docs/guides/8-migration-v1.md[118-129]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The v1 migration guide section "Global convenience functions" lists removed globals, but it omits some functions the PR declares as removed (e.g., `getMongoManager`, `getMongoRepository`). This makes the breaking change documentation incomplete.
## Issue Context
The PR description explicitly enumerates the removed global functions; the migration guide should match that list (or clearly explain why some are documented elsewhere).
## Fix Focus Areas
- docs/docs/guides/8-migration-v1.md[116-145]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The select query builder docs now show dataSource.createQueryBuilder("user"), but
DataSource.createQueryBuilder has no overload that accepts a single string alias; the 1-arg
overload is for QueryRunner, so this example is invalid/misleading.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
.leftJoinAndSelect("user.photos", "photo")

Evidence

DataSource.createQueryBuilder requires (entityClass, alias) when providing an alias. If alias
is omitted, the method treats the first parameter as a QueryRunner and constructs
SelectQueryBuilder with it, meaning a string like "user" is not a valid call. The same doc file
already demonstrates the correct pattern via
dataSource.getRepository(User).createQueryBuilder("user").

src/data-source/DataSource.ts[554-596]
docs/docs/query-builder/1-select-query-builder.md[11-16]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Docs now show `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string alias. This is an invalid example and will confuse users.
### Issue Context
`DataSource.createQueryBuilder` overloads are:
- `(entityClass, alias, queryRunner?)`
- `(queryRunner?)`
So alias-only calls must be via repository (`dataSource.getRepository(User).createQueryBuilder("user")`) or by providing the entity target (`dataSource.createQueryBuilder(User, "user")`).
### Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-809]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

Docs now use dataSource.createQueryBuilder("user"), but DataSource.createQueryBuilder requires
either (entity, alias) or a QueryRunner; a single string argument won’t type-check and can’t
produce the intended aliased query builder.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
.leftJoinAndSelect("user.photos", "photo")

Evidence

The documentation example calls dataSource.createQueryBuilder("user") with a single string
argument. In the actual API, DataSource.createQueryBuilder only overloads to `(entityClass, alias,
queryRunner?) or (queryRunner?); when no alias` is provided, the implementation treats the first
argument as a QueryRunner, so a string is not a valid usage for producing an aliased builder.

docs/docs/query-builder/1-select-query-builder.md[621-629]
src/data-source/DataSource.ts[544-586]
docs/docs/query-builder/1-select-query-builder.md[68-100]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs call `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string argument for creating an aliased query builder.
## Issue Context
`DataSource.createQueryBuilder` requires `(entityTarget, alias)` to build a query builder with `FROM`/`SELECT` preconfigured, or it takes a `QueryRunner` when called with a single argument.
## Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-626]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

MongoDB docs now use dataSource.mongoManager, but the page bootstraps myDataSource; the snippet
references an undefined identifier and will fail if copied.

Code

docs/docs/drivers/mongodb.md[R205-206]

+const manager = dataSource.mongoManager
await manager.save(user)

Evidence

The page defines the DataSource instance as myDataSource, but the updated example uses
dataSource.mongoManager without defining dataSource. This creates a copy/paste runtime failure
in documentation.

docs/docs/drivers/mongodb.md[117-126]
docs/docs/drivers/mongodb.md[192-206]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
MongoDB docs reference `dataSource.mongoManager` but only define `myDataSource`.
## Issue Context
After removing `getMongoManager()`, the example must access the manager via the actual `DataSource` instance variable used in the page.
## Fix Focus Areas
- docs/docs/drivers/mongodb.md[118-126]
- docs/docs/drivers/mongodb.md[205-206]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The v1 migration guide suggests const qb = dataSource.createQueryBuilder("user"), which is not a
valid DataSource.createQueryBuilder usage. This will fail TypeScript type-checking and does not
establish the main alias/from needed for a working query builder.

Code

docs/docs/guides/8-migration-v1.md[R138-139]

+const repo = dataSource.getRepository(User)
+const qb = dataSource.createQueryBuilder("user")

Evidence

The migration guide’s “After” snippet calls dataSource.createQueryBuilder("user") with one
argument, but DataSource.createQueryBuilder requires (entityClass, alias) to create a query
builder with a main alias; the 1-arg overload is for QueryRunner only.

docs/docs/guides/8-migration-v1.md[132-140]
src/data-source/DataSource.ts[547-586]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The migration guide instructs users to replace the removed global `createQueryBuilder("user")` with `dataSource.createQueryBuilder("user")`, which is not a valid overload for `DataSource.createQueryBuilder`.
### Issue Context
`DataSource.createQueryBuilder` requires `(entityClass, alias)` to create a query builder with a main alias (e.g., `"user"`). With one argument, it is the `queryRunner?: QueryRunner` overload.
### Fix Focus Areas
- docs/docs/guides/8-migration-v1.md[132-140]
- src/data-source/DataSource.ts[544-586]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The select query builder docs now show dataSource.createQueryBuilder("user"), but
DataSource.createQueryBuilder has no overload that accepts a single string alias; the 1-arg
overload is for QueryRunner, so this example is invalid/misleading.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
.leftJoinAndSelect("user.photos", "photo")

Evidence

DataSource.createQueryBuilder requires (entityClass, alias) when providing an alias. If alias
is omitted, the method treats the first parameter as a QueryRunner and constructs
SelectQueryBuilder with it, meaning a string like "user" is not a valid call. The same doc file
already demonstrates the correct pattern via
dataSource.getRepository(User).createQueryBuilder("user").

src/data-source/DataSource.ts[554-596]
docs/docs/query-builder/1-select-query-builder.md[11-16]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Docs now show `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string alias. This is an invalid example and will confuse users.
### Issue Context
`DataSource.createQueryBuilder` overloads are:
- `(entityClass, alias, queryRunner?)`
- `(queryRunner?)`
So alias-only calls must be via repository (`dataSource.getRepository(User).createQueryBuilder("user")`) or by providing the entity target (`dataSource.createQueryBuilder(User, "user")`).
### Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-809]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

Docs now use dataSource.createQueryBuilder("user"), but DataSource.createQueryBuilder requires
either (entity, alias) or a QueryRunner; a single string argument won’t type-check and can’t
produce the intended aliased query builder.

Code

docs/docs/query-builder/1-select-query-builder.md[R624-626]

+const user = await dataSource
+    .createQueryBuilder("user")
.leftJoinAndSelect("user.photos", "photo")

Evidence

The documentation example calls dataSource.createQueryBuilder("user") with a single string
argument. In the actual API, DataSource.createQueryBuilder only overloads to `(entityClass, alias,
queryRunner?) or (queryRunner?); when no alias` is provided, the implementation treats the first
argument as a QueryRunner, so a string is not a valid usage for producing an aliased builder.

docs/docs/query-builder/1-select-query-builder.md[621-629]
src/data-source/DataSource.ts[544-586]
docs/docs/query-builder/1-select-query-builder.md[68-100]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs call `dataSource.createQueryBuilder("user")`, but `DataSource.createQueryBuilder` does not accept a single string argument for creating an aliased query builder.
## Issue Context
`DataSource.createQueryBuilder` requires `(entityTarget, alias)` to build a query builder with `FROM`/`SELECT` preconfigured, or it takes a `QueryRunner` when called with a single argument.
## Fix Focus Areas
- docs/docs/query-builder/1-select-query-builder.md[624-626]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

MongoDB docs now use dataSource.mongoManager, but the page bootstraps myDataSource; the snippet
references an undefined identifier and will fail if copied.

<detai...