Add Any Field Type

[kouliavtsev]

In contentlayer 2.7, the string definition would work like any, after the upgrade to 2.8 if the data is not a string an error is thrown. This is correct behavior, yet if you are not able to change the data source you are stuck using contentlayer 2.7.

A good example would be a yaml config file with fields null, true, some string, etc.

// ...
defaultValue: {
  type: "any",
},

# item 1
defaultValue: null
# item 2
defaultValue: true
# item 3
defaultValue: some string

Even though, using any looks like introducing an anti-pattern. I think it has a viable use case.

Similarly, the Add Union Field Type could solve this problem. Yet, it seems a bit harder to implement.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[kouliavtsev]

Would love to see this implemented.

[schickling]

Would the already existing json type work for you? @kouliavtsev

[kouliavtsev]

@schickling

This helped with solving the issue. Thanks a ton!