@mikro-orm/core 6.3.14-dev.18 → 6.3.14-dev.19

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mikro-orm/core",
3
- "version": "6.3.14-dev.18",
3
+ "version": "6.3.14-dev.19",
4
4
  "description": "TypeScript ORM for Node.js based on Data Mapper, Unit of Work and Identity Map patterns. Supports MongoDB, MySQL, PostgreSQL and SQLite databases as well as usage with vanilla JavaScript.",
5
5
  "main": "index.js",
6
6
  "module": "index.mjs",
@@ -64,7 +64,7 @@
64
64
  "esprima": "4.0.1",
65
65
  "fs-extra": "11.2.0",
66
66
  "globby": "11.1.0",
67
- "mikro-orm": "6.3.14-dev.18",
67
+ "mikro-orm": "6.3.14-dev.19",
68
68
  "reflect-metadata": "0.2.2"
69
69
  }
70
70
  }
@@ -23,7 +23,7 @@ export declare class DataloaderUtils {
23
23
  static groupInversedOrMappedKeysByEntityAndOpts(collsWithOpts: readonly [Collection<any>, Omit<InitCollectionOptions<any, any>, 'dataloader'>?][]): Map<string, Map<string, Set<Primary<any>>>>;
24
24
  /**
25
25
  * Turn the entity+options map into actual queries.
26
- * The keys are the entity names + a strigified version of the options and the values are filter Maps which will be used as the values of an $or operator so we end up with a query per entity+opts.
26
+ * The keys are the entity names + a stringified version of the options and the values are filter Maps which will be used as the values of an $or operator so we end up with a query per entity+opts.
27
27
  * We must populate the inverse side of the relationship in order to be able to later retrieve the PK(s) from its item(s).
28
28
  * Together with the query the promises will also return the key which can be used to narrow down the results pertaining to a certain set of options.
29
29
  */
@@ -33,7 +33,7 @@ export declare class DataloaderUtils {
33
33
  * First checks if the Entity type matches, then retrieves the inverse side of the relationship
34
34
  * where the filtering will be done in order to match the target collection.
35
35
  */
36
- static getColFilter<T, S extends T>(collection: Collection<any, object>): (result: T) => result is S;
36
+ static getColFilter<T, S extends T>(collection: Collection<any>): (result: T) => result is S;
37
37
  /**
38
38
  * Returns the collection dataloader batchLoadFn, which aggregates collections by entity,
39
39
  * makes one query per entity and maps each input collection to the corresponding result.
@@ -4,6 +4,7 @@ exports.DataloaderUtils = void 0;
4
4
  const Collection_1 = require("../entity/Collection");
5
5
  const wrap_1 = require("../entity/wrap");
6
6
  const enums_1 = require("../enums");
7
+ const Reference_1 = require("../entity/Reference");
7
8
  class DataloaderUtils {
8
9
  /**
9
10
  * Groups identified references by entity and returns a Map with the
@@ -92,7 +93,7 @@ class DataloaderUtils {
92
93
  }
93
94
  /**
94
95
  * Turn the entity+options map into actual queries.
95
- * The keys are the entity names + a strigified version of the options and the values are filter Maps which will be used as the values of an $or operator so we end up with a query per entity+opts.
96
+ * The keys are the entity names + a stringified version of the options and the values are filter Maps which will be used as the values of an $or operator so we end up with a query per entity+opts.
96
97
  * We must populate the inverse side of the relationship in order to be able to later retrieve the PK(s) from its item(s).
97
98
  * Together with the query the promises will also return the key which can be used to narrow down the results pertaining to a certain set of options.
98
99
  */
@@ -139,20 +140,21 @@ class DataloaderUtils {
139
140
  // There is no need to check if Entity matches because we already matched the key which is entity+options.
140
141
  // This is the inverse side of the relationship where the filtering will be done in order to match the target collection
141
142
  // Either inversedBy or mappedBy exist because we already checked in groupInversedOrMappedKeysByEntity
142
- const refOrCol = result[(collection.property.inversedBy ?? collection.property.mappedBy)];
143
- if (refOrCol instanceof Collection_1.Collection) {
144
- // The inverse side is a Collection
145
- // We keep the result if any of PKs of the inverse side matches the PK of the collection owner
146
- for (const item of refOrCol.getItems()) {
147
- if ((0, wrap_1.helper)(item).getSerializedPrimaryKey() === (0, wrap_1.helper)(collection.owner).getSerializedPrimaryKey()) {
143
+ const inverseProp = collection.property.inversedBy ?? collection.property.mappedBy;
144
+ const target = Reference_1.Reference.unwrapReference(result[inverseProp]);
145
+ if (target instanceof Collection_1.Collection) {
146
+ for (const item of target) {
147
+ if (item === collection.owner) {
148
148
  return true;
149
149
  }
150
150
  }
151
151
  }
152
- else if (refOrCol) {
153
- // The inverse side is a Reference
154
- // We keep the result if the PK of the inverse side matches the PK of the collection owner
155
- return (0, wrap_1.helper)(refOrCol).getSerializedPrimaryKey() === (0, wrap_1.helper)(collection.owner).getSerializedPrimaryKey();
152
+ else if (target) {
153
+ return target === collection.owner;
154
+ }
155
+ // FIXME https://github.com/mikro-orm/mikro-orm/issues/6031
156
+ if (!target && collection.property.kind === enums_1.ReferenceKind.MANY_TO_MANY) {
157
+ throw new Error(`Inverse side is required for M:N relations with dataloader: ${collection.owner.constructor.name}.${collection.property.name}`);
156
158
  }
157
159
  return false;
158
160
  };