Issue: Only 1 dimension allowed in contentTypes

[kristofzerbe]

Describe the bug
In case a Frontmatter subentry has to be taken as name of a custom contentType, it won't work. For example:

FrontMatter

---
title: xxx
subtitle: yyy
photo:
  file: my-photo.jpg
  name: My Photo
---

Setting

"frontMatter.taxonomy.contentTypes": [
	"name": "default",
    "previewPath": "/static/photos/",
	"fields": [
		...
        {
          "title": "Article preview",
          "name": "photo.file",
          "type": "image"
        }
	]
]

Expected behavior
Subentries should be noted if they are separated by a period.

[estruyf]

Thanks @kristofzerbe, this is currently a limitation, but is great to add support in a future version!.

[zivbk1]

I think this would also help resolve #176

[estruyf]

The first integration of the multi-dimensional content-type field support has been added.

In the content type, you can now define it as follows:

{
  "frontMatter.taxonomy.contentTypes": [
    {
      "name": "multi-dimensional",
      "pageBundle": false,
      "fields": [
        ...
        {
          "title": "Photo",
          "type": "fields",
          "name": "photo",
          "fields": [
            {
              "title": "Title",
              "name": "title",
              "type": "string",
              "default": "default title"
            },
            {
              "title": "URL",
              "name": "url",
              "type": "string"
            }
          ]
        }
      ]
    }
  ]
}

When creating the content, it will automatically include the defined fields. From the metadata section in the Front Matter panel, you can perform changes to your article its front matter.

Feel free to test it out in the latest beta version.

[zivbk1]

This is excellent!

[estruyf]

Thanks @zivbk1 for verifying!

@kristofzerbe would you mind giving it a try?

[estruyf]

One small change, the object type has been changed to fields. Additionally, support for taxonomy fields has been added + image fields.

[kristofzerbe]

Thanks @zivbk1 for verifying!

@kristofzerbe would you mind giving it a try?

Custom subfields are working great. Thanks a lot. :)

Only thing is, that I expect in the frontmatter of my posts the file name only (f.e. my-image.png), because I have multiple image folders according to different device classes (mobile, tablet, normal). I tried now to create an image field called preview with a default value like this, to show the small (mobile) image as preview and use it also as preview image in the dashboard:

{
  "title": "Photograph",
  "name": "photograph",
  "type": "fields",
  "fields": [
    {
      "title": "File",
      "name": "file",
      "type": "string",
      "single": true
    },
    {
      "title": "Preview",
      "type": "image",
      "isPreviewImage": true,
      "default": "/static/photos/mobile/{{file}}"
    }
  ]    
}

Maybe the default type works different as I think or I can't use the variable file is this context...

Greets
Kristof