fix(enums): fix nested enum types not having values in forestadmin-schema (#612)

Author: jeffladiray

src/adapters/mongoose.js

@@ -74,6 +74,12 @@ module.exports = async (model, opts) => {
         field.enums = fieldInfo.enumValues;
       }
 
+      if (fieldInfo.enum
+        && Array.isArray(fieldInfo.enum)
+        && fieldInfo.enum.length) {
+        field.enums = fieldInfo.enum;
+      }
+
       type.fields.push(field);
     });
 

test/tests/adapters/expected-results/deep-nested-schema.json

@@ -41,6 +41,14 @@
                 {
                   "field": "depth1Field2Field1",
                   "type": "Boolean"
+                },
+                {
+                  "field": "depth1Field2Field2",
+                  "type": "Enum",
+                  "enums": [
+                    "value1",
+                    "value2"
+                  ]
                 }
               ]
             }

test/tests/adapters/mongoose.test.js

@@ -579,10 +579,22 @@ describe('adapters > schema-adapter', () => {
       expect.assertions(1);
       const schema = new Schema({
         field1: [Date],
-        field2: { field2Field1: Boolean, field2Field2: Number },
+        field2: {
+          field2Field1: Boolean,
+          field2Field2: {
+            type: Number,
+          },
+        },
         depth1: new Schema({
           depth1Field1: [Date],
-          depth1Field2: { depth1Field2Field1: Boolean },
+          depth1Field2: {
+            depth1Field2Field1: Boolean,
+            depth1Field2Field2: {
+              type: String,
+              enum: ['value1', 'value2'],
+              default: 'value1',
+            },
+          },
           depth2: [
             new Schema({
               depth2Field1: [Date],