Nested Enum types do not have values in the schema and crash the Create page in the UI about forest-express-mongoose

[AlexAVL]

@jeffladiray I have just tested the new release and it's working perfectly. Thank you for fixing this and getting it out there so quickly.

[AlexAVL]

I have just confirmed that re-adding these lines to src/adapters/mongoose.js fixes this issue in 7.8.3, but presumably it was removed to fix another issue?

if (fieldInfo.enum && fieldInfo.enum.length) {
  field.enums = fieldInfo.enum;
}

[jeffladiray]

Hey @AlexAVL,
Looks like I'm the culprit here 😅

I'll take a look in our issue tracker to refresh my memory, but I remember that this small changes was actually a long term discussion.

While I'm looking for a deeper analysis of this issue, would you mind testing with the condition mentionned in the PR and tell me if it actually works on your end?

(fieldInfo.enum
        && Array.isArray(fieldInfo.enum)
        && fieldInfo.enumValues.length)

Thanks in advance

(As a side note, I also suggest you to open a ticket on our discourse community (Here) next time, we're more active there 🙌 )

[AlexAVL]

Hi @jeffladiray,

Thanks for the quick response, and I'll remember Discourse for next time.

That snippet didn't quite work, because enumValues is not defined and trying to get a length for it throws an error. I guessed it might be a typo, and trying this one did work just fine:

if (fieldInfo.enum
  && Array.isArray(fieldInfo.enum)
  && fieldInfo.enum.length) {
  field.enums = fieldInfo.enum;
}

After adding that the values are in the forestadmin-schema.json and the UI works again.

The code that creates the mongoose schema and creates this situation is approximately this:

const possibleValues = ['value1', 'value2'];
const defaultValue = 'value1';

const configSchema = new mongoose.Schema(
  {
    subFieldName: {
      type: String,
      enum: possibleValues,
      default: defaultValue,
    },
  },
  { _id: false },
);

const itemSchema = new mongoose.Schema(
  {
    configuration: configSchema,
  },
  {
    timestamps: true,
  },
);

Thanks for your help with this.

[forest-bot]

🎉 This issue has been resolved in version 7.8.5 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release
• v7.8.5

Your semantic-release bot 📦🚀

[jeffladiray]

The fix is released. Let me know if you're still experiencing the issue 👍

[forest-bot]

🎉 This issue has been resolved in version 8.0.0-beta.5 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release
• v8.0.0-beta.5

Your semantic-release bot 📦🚀