Enum values are not validated

[lluiscab]

I've seen some examples on issues of people using a field of type enum to specify the page locale.

---
locale: 'en'
---
(...)

defineDocumentType(() => ({
    [...],
    fields: {
        locale: {
            type: 'enum',
            options: ['en', 'es', 'de'],
            required: true
        }
    }
}));

I've just seen on contentlayer@0.3.0 that if you have a file with an invalid enum value (not in the options array), then the build will complete successfully.

---
locale: 'not in the options array'
---
(...)

$ yarn contentlayer build
yarn run v1.22.19
$ /(...)/node_modules/.bin/contentlayer build
Generated 2 documents in .contentlayer
Done in 1.32s.

I understand that even if it does not validate values, the enum type field is really useful once it automatically generates TS types, but given that we can validate fields with required, shouldn't we also be able to validate the if the field value matches what we defined on the schema? (In the case of enum fields)

[kouliavtsev]

@schickling

This would be an amazing feature (warning value does not match enum) since you can import configuration files and validate if the content writer has picked the correct tags, categories, etc.

import someConfig from "./config/someConfig";

...
    test: {
      type: "enum",
      options: someConfig.map((item) => item.example),
      default: someConfig[1],
    },

The import someConfig from "./config/someConfig"; can now be used where you know that the values are valid.