@solidstarters/solid-core 1.2.18 → 1.2.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.
@@ -0,0 +1,43 @@
1
+ // many-to-one field
2
+ // {
3
+ // "name": "module",
4
+ // "displayName": "Module",
5
+ // "type": "relation",
6
+ // "required": true,
7
+ // "unique": false,
8
+ // "index": true,
9
+ // "private": false,
10
+ // "encrypt": false,
11
+ // "relationType": "many-to-one",
12
+ // "relationModelSingularName": "moduleMetadata",
13
+ // "relationCreateInverse": true,
14
+ // "relationCascade": "set null",
15
+ // "relationModelModuleName": "solid-core",
16
+ // "isSystem": true
17
+ // },
18
+
19
+ // one-to-many field
20
+ // {
21
+ // "name": field.relationModelField,
22
+ // Logic to create a oneToMany field definition
23
+ // return [
24
+ // "name",
25
+ // "displayName",
26
+ // "description",
27
+ // "type",
28
+ // "ormType",
29
+ // "isSystem",
30
+ // "relationType",
31
+ // "relationModelFieldName",
32
+ // "relationCreateInverse",
33
+ // "relationModelSingularName",
34
+ // "relationModelModuleName",
35
+ // "required",
36
+ // "unique",
37
+ // "index",
38
+ // "private",
39
+ // "encrypt",
40
+ // "encryptionType",
41
+ // "decryptWhen",
42
+ // "columnName"
43
+ // ];
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@solidstarters/solid-core",
3
- "version": "1.2.18",
3
+ "version": "1.2.19",
4
4
  "description": "This module is a NestJS module containing all the required core providers required by a Solid application",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",
@@ -0,0 +1,6 @@
1
+ 1. Do i need to create a storeStreams method for aws service too?
2
+ - Handle later
3
+ 2. queues handling -> if queues is enabled by default, i.e triggerExport(exportTransactionEntity.id).
4
+ - startExport should either return the data or return the transaction id
5
+ 3. How to handle scenarios wherein, nested related exist.(do i need to only get the userkey)
6
+ - show the userKey
@@ -311,7 +311,7 @@ export class CRUDService<T> { //Add two generic value i.e Person,CreatePersonDto
311
311
  const manyToOneOptions: ManyToOneRelationFieldOptions = {
312
312
  ...commonOptions,
313
313
  relationModelSingularName: fieldMetadata.relationModelSingularName,
314
- modelUserKeyFieldName: fieldMetadata.model.userKeyField.name,
314
+ modelUserKeyFieldName: fieldMetadata.model.userKeyField?.name,
315
315
  modelSingularName: fieldMetadata.model.singularName,
316
316
  entityManager,
317
317
  }
@@ -1,21 +0,0 @@
1
- {
2
- // Use IntelliSense to learn about possible attributes.
3
- // Hover to view descriptions of existing attributes.
4
- // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
5
- "version": "0.2.0",
6
- "configurations": [
7
-
8
- {
9
- "type": "node",
10
- "request": "launch",
11
- "name": "Launch Program",
12
- "skipFiles": [
13
- "<node_internals>/**"
14
- ],
15
- "program": "${workspaceFolder}/dist/index.js",
16
- "outFiles": [
17
- "${workspaceFolder}/**/*.js"
18
- ]
19
- }
20
- ]
21
- }