Enhancement: Editor for data files in the Hugo 'data' folder. #153

New Issue

Closed

opened 2026-10-05 02:29:55 +02:00 by adam · 20 comments

adam commented 2026-10-05 02:29:55 +02:00

Owner

Copy link

Copy source

Is your feature request related to a problem? Please describe.

I have a site where there are data files (JSON) used to drive the content in tables.
https://gohugo.io/templates/data-templates/

Describe the solution you'd like

I would like to describe the data model in the files like I do now with content types, and then have a UI to edit the information in the files with a GUI.

Describe alternatives you've considered

I can edit the plain text files by hand, but what's the fun in that? Also, asking my editors to write JSON, YAML, TOML, etc. by hand is a bit much.

Additional context

Here is an example of a UI for the JSON content below.

{
  "columns": [
    "Rating",
    "Credit Score"
  ],
  "rows": [
    {
      "cells": [
        "A++",
        "750+"
      ]
    },
    {
      "cells": [
        "A+",
        "710 - 749"
      ]
    },
    {
      "cells": [
        "A",
        "680 - 709"
      ]
    },
    {
      "cells": [
        "B",
        "650 - 679 up to 80% LTV"
      ]
    },
    {
      "cells": [
        "C",
        "620 - 649 up to 70% LTV"
      ]
    }
  ]
}

**Is your feature request related to a problem? Please describe.** I have a site where there are data files (JSON) used to drive the content in tables. https://gohugo.io/templates/data-templates/ **Describe the solution you'd like** I would like to describe the data model in the files like I do now with content types, and then have a UI to edit the information in the files with a GUI. **Describe alternatives you've considered** I can edit the plain text files by hand, but what's the fun in that? Also, asking my editors to write JSON, YAML, TOML, etc. by hand is a bit much. **Additional context** Here is an example of a UI for the JSON content below.  ``` { "columns": [ "Rating", "Credit Score" ], "rows": [ { "cells": [ "A++", "750+" ] }, { "cells": [ "A+", "710 - 749" ] }, { "cells": [ "A", "680 - 709" ] }, { "cells": [ "B", "650 - 679 up to 80% LTV" ] }, { "cells": [ "C", "620 - 649 up to 70% LTV" ] } ] } ``` <!-- github-sync-id:1063699096 -->

adam closed this issue 2026-10-05 02:29:55 +02:00

adam commented 2026-10-05 02:29:56 +02:00

Author

Owner

Copy link

Copy source

Thinking about this one, what if you can define data types via the settings like:

{
  "frontMatter.data.types": [
    {
      "name": "sponsors",
      "file": "[workspace]/data/sponsors.json",
      "schema": {
        "title": "Sponsors",
        "type": "object",
        "required": [
          "url",
          "name",
          "avatar"
        ],
        "properties": {
          "url": {
            "type": "string",
            "title": "URL"
          },
          "name": {
            "type": "string",
            "title": "Name"
          },
          "avatar": {
            "type": "string",
            "title": "Avatar"
          }
        }
      }
    }
  ]
}

If there is data defined like this, the extension would render a new data tab and allow you to start editing the content.

Thinking about this one, what if you can define data types via the settings like: ``` { "frontMatter.data.types": [ { "name": "sponsors", "file": "[workspace]/data/sponsors.json", "schema": { "title": "Sponsors", "type": "object", "required": [ "url", "name", "avatar" ], "properties": { "url": { "type": "string", "title": "URL" }, "name": { "type": "string", "title": "Name" }, "avatar": { "type": "string", "title": "Avatar" } } } } ] } ``` If there is data defined like this, the extension would render a new `data` tab and allow you to start editing the content. <!-- github-comment-id:1011198803 -->

adam commented 2026-10-05 02:29:56 +02:00

Author

Owner

Copy link

Copy source

@zivbk1 been working on a new data dashboard.

What do you think?

Settings

The settings look as follows:

{
	"frontMatter.data.files": [
    {
      "id": "sponsors",
      "title": "Sponsors",
      "file": "[[workspace]]/data/sponsors.json",
      "labelField": "name",
      "schema": {
        "title": "Sponsors",
        "type": "object",
        "required": [
          "url",
          "name",
          "avatar"
        ],
        "properties": {
          "url": {
            "type": "string",
            "title": "URL"
          },
          "name": {
            "type": "string",
            "title": "Name"
          },
          "avatar": {
            "type": "string",
            "title": "Avatar"
          }
        }
      }
    },
    {
      "id": "projects",
      "title": "Projects",
      "file": "[[workspace]]/themes/eliostruyf-v2/data/projects.json",
      "labelField": "title",
      "schema": {
        "title": "Projects",
        "type": "object",
        "required": [
          "title",
          "href"
        ],
        "properties": {
          "title": {
            "type": "string",
            "title": "Title"
          },
          "href": {
            "type": "string",
            "title": "Link"
          }
        }
      }
    }
  ]
}

@zivbk1 been working on a new data dashboard. What do you think?  **Settings** The settings look as follows: ```json { "frontMatter.data.files": [ { "id": "sponsors", "title": "Sponsors", "file": "[[workspace]]/data/sponsors.json", "labelField": "name", "schema": { "title": "Sponsors", "type": "object", "required": [ "url", "name", "avatar" ], "properties": { "url": { "type": "string", "title": "URL" }, "name": { "type": "string", "title": "Name" }, "avatar": { "type": "string", "title": "Avatar" } } } }, { "id": "projects", "title": "Projects", "file": "[[workspace]]/themes/eliostruyf-v2/data/projects.json", "labelField": "title", "schema": { "title": "Projects", "type": "object", "required": [ "title", "href" ], "properties": { "title": { "type": "string", "title": "Title" }, "href": { "type": "string", "title": "Link" } } } } ] } ``` <!-- github-comment-id:1012427427 -->

adam commented 2026-10-05 02:29:57 +02:00

Author

Owner

Copy link

Copy source

@estruyf can you use wildcards to match all .json files in a particular folder?
Ex. [[workspace]]/data/tables/*.json

Matches all of these files in the tables folder...

@estruyf can you use wildcards to match all .json files in a particular folder? Ex. `[[workspace]]/data/tables/*.json` Matches all of these files in the tables folder...  <!-- github-comment-id:1012638046 -->

adam commented 2026-10-05 02:29:58 +02:00

Author

Owner

Copy link

Copy source

@estruyf how would I represent this data structure in frontmatter.data.files?

{
  "name": "Credit-HELOC",
  "columns": [
    "Rating",
    "Credit Score"
  ],
  "rows": [
    {
      "cells": [
        "A++",
        "750+"
      ]
    },
    {
      "cells": [
        "A+",
        "710 - 749"
      ]
    },
    {
      "cells": [
        "A",
        "680 - 709"
      ]
    },
    {
      "cells": [
        "B",
        "650 - 679 up to 80% LTV"
      ]
    },
    {
      "cells": [
        "C",
        "620 - 649 up to 70% LTV"
      ]
    }
  ]
}

@estruyf how would I represent this data structure in `frontmatter.data.files`? ``` { "name": "Credit-HELOC", "columns": [ "Rating", "Credit Score" ], "rows": [ { "cells": [ "A++", "750+" ] }, { "cells": [ "A+", "710 - 749" ] }, { "cells": [ "A", "680 - 709" ] }, { "cells": [ "B", "650 - 679 up to 80% LTV" ] }, { "cells": [ "C", "620 - 649 up to 70% LTV" ] } ] } ``` <!-- github-comment-id:1012640454 -->

adam commented 2026-10-05 02:29:59 +02:00

Author

Owner

Copy link

Copy source

@estruyf can you use wildcards to match all .json files in a particular folder? Ex. [[workspace]]/data/tables/*.json

Matches all of these files in the tables folder...

For now, the data files would have to be defined in the settings. The definition is required to correctly render the form.

> @estruyf can you use wildcards to match all .json files in a particular folder? Ex. `[[workspace]]/data/tables/*.json` > > Matches all of these files in the tables folder... For now, the data files would have to be defined in the settings. The definition is required to correctly render the form. <!-- github-comment-id:1012860884 -->

adam commented 2026-10-05 02:29:59 +02:00

Author

Owner

Copy link

Copy source

@estruyf how would I represent this data structure in frontmatter.data.files?

...

More testing is required and for sure some styling is missing for lists. The schema for your data would looks as follows:

{
  "id": "test",
  "file": "[[workspace]]/data/tests.json",
  "labelField": "title",
  "title": "Test",
  "schema": {
    "type": "object",
    "properties": {
      "name": {
        "type": "string"
      },
      "columns": {
        "type": "array",
        "items": { "type": "string" }
      },
      "rows": {
        "type": "array",
        "items": {
          "type": "object",
          "properties": {
            "cells": {
              "type": "array",
              "items": { "type": "string" }
            }
          }
        }
      }
    }
  }
}

> @estruyf how would I represent this data structure in `frontmatter.data.files`? > > ... More testing is required and for sure some styling is missing for lists. The schema for your data would looks as follows: ```json { "id": "test", "file": "[[workspace]]/data/tests.json", "labelField": "title", "title": "Test", "schema": { "type": "object", "properties": { "name": { "type": "string" }, "columns": { "type": "array", "items": { "type": "string" } }, "rows": { "type": "array", "items": { "type": "object", "properties": { "cells": { "type": "array", "items": { "type": "string" } } } } } } } } ``` <!-- github-comment-id:1012913858 -->

adam commented 2026-10-05 02:30:00 +02:00

Author

Owner

Copy link

Copy source

@estruyf can you use wildcards to match all .json files in a particular folder? Ex. [[workspace]]/data/tables/*.json
Matches all of these files in the tables folder...

For now, the data files would have to be defined in the settings. The definition is required to correctly render the form.

Is it possible to define a structure for a data file once, then for each file in the folder indicate that the same structure is used. Repeating the whole structure in the configuration file for every file doesn't seem practical. I'm thinking of a way to say "Everything in this folder has this data structure."

> > @estruyf can you use wildcards to match all .json files in a particular folder? Ex. `[[workspace]]/data/tables/*.json` > > Matches all of these files in the tables folder... > > For now, the data files would have to be defined in the settings. The definition is required to correctly render the form. Is it possible to define a structure for a data file once, then for each file in the folder indicate that the same structure is used. Repeating the whole structure in the configuration file for every file doesn't seem practical. I'm thinking of a way to say "Everything in this folder has this data structure." <!-- github-comment-id:1012963675 -->

adam commented 2026-10-05 02:30:01 +02:00

Author

Owner

Copy link

Copy source

That would mean files and types need to be split up. So you can have data types, to define the schema, and data files to specify the location and defined type ID.

That would mean files and types need to be split up. So you can have data types, to define the schema, and data files to specify the location and defined type ID. <!-- github-comment-id:1012968340 -->

adam commented 2026-10-05 02:30:02 +02:00

Author

Owner

Copy link

Copy source

That would mean files and types need to be split up. So you can have data types, to define the schema, and data files to specify the location and defined type ID.

I like that idea. I could also see something like this working with a new Frontmatter field type that lets you define a set of defined data structures to pick from as a template, and add into an array. This concept would resolve the other issue I have for "blocks" (page_sections) stored in Front matter data. #176

> That would mean files and types need to be split up. So you can have data types, to define the schema, and data files to specify the location and defined type ID. I like that idea. I could also see something like this working with a new Frontmatter field type that lets you define a set of defined data structures to pick from as a template, and add into an array. This concept would resolve the other issue I have for "blocks" (page_sections) stored in Front matter data. #176 <!-- github-comment-id:1012971769 -->

adam commented 2026-10-05 02:30:02 +02:00

Author

Owner

Copy link

Copy source

Support for arrays has been added as well:

This allows you to at least use the configuration from above. I'll see what I can do for the type and file splitting.

Support for arrays has been added as well:  This allows you to at least use the configuration from above. I'll see what I can do for the `type` and `file` splitting. <!-- github-comment-id:1012977301 -->

adam commented 2026-10-05 02:30:03 +02:00

Author

Owner

Copy link

Copy source

@zivbk1 data type support has been added. You can specify the schema on file level or on the type level.

On file level is easy when you'll use it a single time, when defining it on type level, you can reuse it.

"frontMatter.data.files": [
	  {
	    "id": "test",
	    "file": "[[workspace]]/data/tests.json",
	    "labelField": "name",
	    "title": "Test",
	    "type": "genericContent"
	  }
],
"frontMatter.data.types": [
	  {
	    "id": "genericContent",
	    "schema": {
	      "type": "object",
	      "properties": {
	        "name": {
	          "type": "string"
	        },
	        "columns": {
	          "type": "array",
	          "items": { "type": "string" }
	        },
	        "rows": {
	          "type": "array",
	          "items": {
	            "type": "object",
	            "properties": {
	              "cells": {
	                "type": "array",
	                "items": { "type": "string" }
	              }
	            }
	          }
	        }
	      }
	    }
	  }
]

Hope this will make it easier for you.

@zivbk1 data type support has been added. You can specify the schema on file level or on the type level. On file level is easy when you'll use it a single time, when defining it on type level, you can reuse it. ```json "frontMatter.data.files": [ { "id": "test", "file": "[[workspace]]/data/tests.json", "labelField": "name", "title": "Test", "type": "genericContent" } ], "frontMatter.data.types": [ { "id": "genericContent", "schema": { "type": "object", "properties": { "name": { "type": "string" }, "columns": { "type": "array", "items": { "type": "string" } }, "rows": { "type": "array", "items": { "type": "object", "properties": { "cells": { "type": "array", "items": { "type": "string" } } } } } } } } ] ``` Hope this will make it easier for you. <!-- github-comment-id:1013060652 -->

adam commented 2026-10-05 02:30:04 +02:00

Author

Owner

Copy link

Copy source

As discussed, I will add another setting frontMatter.data.folders. This setting will allow the extension to load all files from the folder and use the same data type

As discussed, I will add another setting `frontMatter.data.folders`. This setting will allow the extension to load all files from the folder and use the same data type <!-- github-comment-id:1013291848 -->

adam commented 2026-10-05 02:30:05 +02:00

Author

Owner

Copy link

Copy source

@estruyf realy nice project. i have tested the datafolder and can confrim it works.

Can you give me a hint for a good yaml to json scheme editor from an example yaml file?

i am thinking somtehing like a yaml file and to generate a schema from this example file?

entries:
- title: sidebar
  product: Jekyll Doc Theme
  version: 6.0
  folders:

  - title:
    output: pdf
    type: frontmatter
    folderitems:
    - title:
      url: /titlepage.html
      output: pdf
      type: frontmatter
    - title:
      url: /tocpage.html
      output: pdf
      type: frontmatter

  - title: Overview
 ...

or from a json example file

{
  "entries": [
    {
      "title": "sidebar",
      "product": "Jekyll Doc Theme",
      "version": 6,
      "folders": [
        {
          "title": null,
          "output": "pdf",
          "type": "frontmatter",
          "folderitems": [
            {
              "title": null,
              "url": "/titlepage.html",
              "output": "pdf",
              "type": "frontmatter"
            },
            {
              "title": null,
              "url": "/tocpage.html",
              "output": "pdf",
              "type": "frontmatter"
            }
          ]
        },
        {
          "title": "Overview",
          "output": "web, pdf",

...

i have tried to generate a schema for this example file, and did not get it work.

entries:
  - title: other
    folders:
      - title: Other Links
        folderitems:
          - title: Automated links bookmark
            url: /bookmark_one.html
          - title: Bookmark links
            url: /bookmarks.html
          - title: Some link bookmark
            url: /other.html

 "frontMatter.data.types": [
...
   {
      "id": "genericContent1",
      "schema": {
        "type": "object",
        "additionalProperties": false,
        "properties": {
          "entries": {
            "type": "array",
            "items": {
              "$ref": "#/definitions/Entry"
            }
          }
        },
        "required": [
          "entries"
        ]

      },
      "Entry": {
        "type": "object",
        "additionalProperties": false,
        "properties": {
          "title": {
            "type": "string"
          },
          "folders": {
            "type": "array",
            "items": {
              "$ref": "#/definitions/Folder"
            }
          }
        },
        "required": [
          "folders",
          "title"
        ],
        "title": "Entry"
      },
      "Folder": {
        "type": "object",
        "additionalProperties": false,
        "properties": {
          "title": {
            "type": "string"
          },
          "folderitems": {
            "type": "array",
            "items": {
              "$ref": "#/definitions/Folderitem"
            }
          }
        },
        "required": [
          "folderitems",
          "title"
        ],
        "title": "Folder"
      },
      "Folderitem": {
        "type": "object",
        "additionalProperties": false,
        "properties": {
          "title": {
            "type": "string"
          },
          "url": {
            "type": "string"
          }
        },
        "required": [
          "title",
          "url"
        ],
        "title": "Folderitem"
      }
    }
  ]

@estruyf realy nice project. i have tested the datafolder and can confrim it works. Can you give me a hint for a good yaml to json scheme editor from an example yaml file? i am thinking somtehing like a yaml file and to generate a schema from this example file? ```yaml entries: - title: sidebar product: Jekyll Doc Theme version: 6.0 folders: - title: output: pdf type: frontmatter folderitems: - title: url: /titlepage.html output: pdf type: frontmatter - title: url: /tocpage.html output: pdf type: frontmatter - title: Overview ... ``` or from a json example file ```json { "entries": [ { "title": "sidebar", "product": "Jekyll Doc Theme", "version": 6, "folders": [ { "title": null, "output": "pdf", "type": "frontmatter", "folderitems": [ { "title": null, "url": "/titlepage.html", "output": "pdf", "type": "frontmatter" }, { "title": null, "url": "/tocpage.html", "output": "pdf", "type": "frontmatter" } ] }, { "title": "Overview", "output": "web, pdf", ... ``` i have tried to generate a schema for this example file, and did not get it work. ```yaml entries: - title: other folders: - title: Other Links folderitems: - title: Automated links bookmark url: /bookmark_one.html - title: Bookmark links url: /bookmarks.html - title: Some link bookmark url: /other.html ``` ```json "frontMatter.data.types": [ ... { "id": "genericContent1", "schema": { "type": "object", "additionalProperties": false, "properties": { "entries": { "type": "array", "items": { "$ref": "#/definitions/Entry" } } }, "required": [ "entries" ] }, "Entry": { "type": "object", "additionalProperties": false, "properties": { "title": { "type": "string" }, "folders": { "type": "array", "items": { "$ref": "#/definitions/Folder" } } }, "required": [ "folders", "title" ], "title": "Entry" }, "Folder": { "type": "object", "additionalProperties": false, "properties": { "title": { "type": "string" }, "folderitems": { "type": "array", "items": { "$ref": "#/definitions/Folderitem" } } }, "required": [ "folderitems", "title" ], "title": "Folder" }, "Folderitem": { "type": "object", "additionalProperties": false, "properties": { "title": { "type": "string" }, "url": { "type": "string" } }, "required": [ "title", "url" ], "title": "Folderitem" } } ] ``` <!-- github-comment-id:1013864698 -->

adam commented 2026-10-05 02:30:05 +02:00

Author

Owner

Copy link

Copy source

@wemasoe easiest is to use a JSON to YAML converter.

I converted the JSON object, to the following schema:

{
  "type": "object",
  "properties": {
    "entries": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "title": {
            "type": "string"
          },
          "output": {
            "type": "string"
          },
          "type": {
            "type": "string"
          },
          "folderitems": {
            "type": "array",
            "items": {
              "type": "object",
              "properties": {
                "title": {
                  "type": "string"
                },
                "url": {
                  "type": "string"
                },
                "output": {
                  "type": "string"
                },
                "type": {
                  "type": "string"
                }
              }
            }
          }
        }
      }
    }
  },
  "additionalProperties": false,
  "required": [
    "entries"
  ]
}

@wemasoe easiest is to use a JSON to YAML converter. I converted the JSON object, to the following schema: ```JSON { "type": "object", "properties": { "entries": { "type": "array", "items": { "type": "object", "properties": { "title": { "type": "string" }, "output": { "type": "string" }, "type": { "type": "string" }, "folderitems": { "type": "array", "items": { "type": "object", "properties": { "title": { "type": "string" }, "url": { "type": "string" }, "output": { "type": "string" }, "type": { "type": "string" } } } } } } } }, "additionalProperties": false, "required": [ "entries" ] } ``` <!-- github-comment-id:1013933248 -->

adam commented 2026-10-05 02:30:06 +02:00

Author

Owner

Copy link

Copy source

@wemasoe easiest is to use a JSON to YAML converter.

I converted the JSON object, to the following schema:

{
  "type": "object",
  "properties": {
    "entries": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "title": {
            "type": "string"
          },
          "output": {
            "type": "string"
          },
          "type": {
            "type": "string"
          },
          "folderitems": {
            "type": "array",
            "items": {
              "type": "object",
              "properties": {
                "title": {
                  "type": "string"
                },
                "url": {
                  "type": "string"
                },
                "output": {
                  "type": "string"
                },
                "type": {
                  "type": "string"
                }
              }
            }
          }
        }
      }
    }
  },
  "additionalProperties": false,
  "required": [
    "entries"
  ]
}

sorry to say the schema did not work.

i dont get any data entry in the data tab for this file.

Your other.yaml data items
No other.yaml data entries found

Create or modify your other.yaml data
Add new data
Entries

source file:

entries:
  - title: other
    folders:
      - title: Other Links
        folderitems:
          - title: Automated links bookmark
            url: /bookmark_one.html
          - title: Bookmark links
            url: /bookmarks.html
          - title: Some link bookmark
            url: /other.html

when adding an entry old entries are gone.

- entries:
    - title: new title
      output: output
      type: type
      folderitems:
        - title: folderitem title
          url: folder item url
          output: folder item outpur
          type: folderitem type

i just want to reply to your help and give a feedback.

> @wemasoe easiest is to use a JSON to YAML converter. > > I converted the JSON object, to the following schema: > > ```json > { > "type": "object", > "properties": { > "entries": { > "type": "array", > "items": { > "type": "object", > "properties": { > "title": { > "type": "string" > }, > "output": { > "type": "string" > }, > "type": { > "type": "string" > }, > "folderitems": { > "type": "array", > "items": { > "type": "object", > "properties": { > "title": { > "type": "string" > }, > "url": { > "type": "string" > }, > "output": { > "type": "string" > }, > "type": { > "type": "string" > } > } > } > } > } > } > } > }, > "additionalProperties": false, > "required": [ > "entries" > ] > } > ``` sorry to say the schema did not work. i dont get any data entry in the data tab for this file. ```plantuml Your other.yaml data items No other.yaml data entries found Create or modify your other.yaml data Add new data Entries ``` source file: ```yaml entries: - title: other folders: - title: Other Links folderitems: - title: Automated links bookmark url: /bookmark_one.html - title: Bookmark links url: /bookmarks.html - title: Some link bookmark url: /other.html ``` when adding an entry old entries are gone. ```yaml - entries: - title: new title output: output type: type folderitems: - title: folderitem title url: folder item url output: folder item outpur type: folderitem type ``` i just want to reply to your help and give a feedback. <!-- github-comment-id:1014819067 -->

adam commented 2026-10-05 02:30:07 +02:00

Author

Owner

Copy link

Copy source

Recreated it with the new sample you gave, and the following schema can create your data structure:

{
  "id": "data-entries",
  "title": "Data Entries",
  "file": "[[workspace]]/data/data-entries.yml",
  "fileType": "yaml",
  "schema": {
    "type": "object",
    "properties": {
      "entries": {
        "type": "object",
        "properties": {
          "title": {
            "type": "string"
          },
          "folders": {
            "type": "array",
            "items": {
              "type": "object",
              "properties": {
                "title": {
                  "type": "string"
                },
                "output": {
                  "type": "string"
                },
                "type": {
                  "type": "string"
                },
                "folderitems": {
                  "type": "array",
                  "items": {
                    "type": "object",
                    "properties": {
                      "title": {
                        "type": "string"
                      },
                      "url": {
                        "type": "string"
                      },
                      "output": {
                        "type": "string"
                      },
                      "type": {
                        "type": "string"
                      }
                    }
                  }
                }
              }
            }
          }
        }
      }
    },
    "additionalProperties": false,
    "required": [
      "entries"
    ]
  }
}

Recreated it with the new sample you gave, and the following schema can create your data structure: ```json { "id": "data-entries", "title": "Data Entries", "file": "[[workspace]]/data/data-entries.yml", "fileType": "yaml", "schema": { "type": "object", "properties": { "entries": { "type": "object", "properties": { "title": { "type": "string" }, "folders": { "type": "array", "items": { "type": "object", "properties": { "title": { "type": "string" }, "output": { "type": "string" }, "type": { "type": "string" }, "folderitems": { "type": "array", "items": { "type": "object", "properties": { "title": { "type": "string" }, "url": { "type": "string" }, "output": { "type": "string" }, "type": { "type": "string" } } } } } } } } } }, "additionalProperties": false, "required": [ "entries" ] } } ```  <!-- github-comment-id:1015284879 -->

adam commented 2026-10-05 02:30:07 +02:00

Author

Owner

Copy link

Copy source

@estruyf thx a lot :-)
json schema is not as easy as it seems. hope i will understand it sometime.

@estruyf thx a lot :-) json schema is not as easy as it seems. hope i will understand it sometime. <!-- github-comment-id:1016848012 -->

adam commented 2026-10-05 02:30:08 +02:00

Author

Owner

Copy link

Copy source

i have set it for a folder and can confirm it works. Although in "frontMatter.data.types": [ a file is set in the json schema "file": "[[workspace]]/data/data-entries.yml",

 "frontMatter.data.types": [
    {
...
{
  "id": "data-entries",
  "title": "Data Entries",
  "file": "[[workspace]]/data/data-entries.yml",
  "fileType": "yaml",
  "schema": {
    "type": "object",
    "properties": {
      "entries": {
        "type": "object",
        "properties": {
          "title": {
            "type": "string"
          },
          "folders": {
...

  "frontMatter.data.folders": [
    {
      "id": "test1folder",
      "path": "[[workspace]]/data/",
      "labelField": "name",
      "type": "data-entries"
    }
  ],

i have set it for a folder and can confirm it works. Although in ```"frontMatter.data.types": [``` a file is set in the json schema ``` "file": "[[workspace]]/data/data-entries.yml",``` ```json "frontMatter.data.types": [ { ... { "id": "data-entries", "title": "Data Entries", "file": "[[workspace]]/data/data-entries.yml", "fileType": "yaml", "schema": { "type": "object", "properties": { "entries": { "type": "object", "properties": { "title": { "type": "string" }, "folders": { ... ``` ```json "frontMatter.data.folders": [ { "id": "test1folder", "path": "[[workspace]]/data/", "labelField": "name", "type": "data-entries" } ], ``` <!-- github-comment-id:1016853066 -->

adam commented 2026-10-05 02:30:09 +02:00

Author

Owner

Copy link

Copy source

@estruyf thx a lot :-) JSON schema is not as easy as it seems. hope I will understand it sometime.

I understand, there are PROs and CONs on each schema/approach to use. I also validated Simple Schema, which seems "simple", but complicates objects IMO. That is why I picked JSON schema.

> @estruyf thx a lot :-) JSON schema is not as easy as it seems. hope I will understand it sometime. I understand, there are PROs and CONs on each schema/approach to use. I also validated Simple Schema, which seems "simple", but complicates objects IMO. That is why I picked JSON schema. <!-- github-comment-id:1017241927 -->

adam commented 2026-10-05 02:30:10 +02:00

Author

Owner

Copy link

Copy source

i have set it for a folder and can confirm it works. Although in "frontMatter.data.types": [ a file is set in the json schema "file": "[[workspace]]/data/data-entries.yml",

Documentation for these new settings is on its way (still needs to be written before releasing v6).

• frontMatter.data.types: This only defines the object and its fields. There is no reference to any file or folder. It has two properties: id and schema
• frontMatter.data.files: Defines how a single file needs to be handled. It can use a schema or an ID of the data type.
• frontMatter.data.folders: Defines that all files from a folder need to be handled the same. It can use a schema or an ID of the data type.

In your case, you better define the type via the frontMatter.data.types setting and reuse it in the file and folders setting.

> i have set it for a folder and can confirm it works. Although in `"frontMatter.data.types": [` a file is set in the json schema ` "file": "[[workspace]]/data/data-entries.yml",` Documentation for these new settings is on its way (still needs to be written before releasing v6). - `frontMatter.data.types`: This only defines the object and its fields. There is no reference to any file or folder. It has two properties: `id` and `schema` - `frontMatter.data.files`: Defines how a single file needs to be handled. It can use a schema or an ID of the data type. - `frontMatter.data.folders`: Defines that all files from a folder need to be handled the same. It can use a schema or an ID of the data type. In your case, you better define the type via the `frontMatter.data.types` setting and reuse it in the file and folders setting. <!-- github-comment-id:1017248019 -->

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

beta

dependabot/npm_and_yarn/js-yaml-4.3.1

dependabot/npm_and_yarn/multi-7958ac4c45

dependabot/npm_and_yarn/postcss-8.5.25

dependabot/npm_and_yarn/multi-670d462a53

dependabot/npm_and_yarn/http-proxy-middleware-2.0.10

dependabot/npm_and_yarn/shell-quote-1.10.0

dependabot/npm_and_yarn/websocket-driver-0.7.5

dependabot/npm_and_yarn/multi-6aaed2ab8e

copilot/validate-issue-1043

dependabot/npm_and_yarn/multi-84120a5570

dependabot/npm_and_yarn/launch-editor-2.14.1

dependabot/npm_and_yarn/multi-9dd3b9b346

estruyf/smart-file-rename

copilot/fix-unwanted-auto-update-publish-date

copilot/fix-content-view-sorting-issue

copilot/fix-virtual-workspace-folder-selection

copilot/fix-937

copilot/fix-965

copilot/fix-958

copilot/fix-950

copilot/fix-932

copilot-integration

hotfix/10.2.1

issue/816

issue/671

i18n

azure-translator

issue/747

issue/673

poc/content-tagging

combobox

v10.13.0

v10.12.0

v10.11.0

v10.10.1

v10.10.0

v10.9.0

v10.8.0

v10.7.0

v10.6.0

v10.5.1

v10.5.0

v10.4.1

v10.4.0

v10.3.0

v10.2.1

v10.2.0

v10.1.0

v10.0.2

v10.0.1

v10.0.0

v9.4.0

v9.3.1

v9.3.0

v9.2.0

v9.1.0

v9.0.0

v8.4.0

v8.3.0

v8.2.0

v8.1.2

v8.1.1

v8.1.0

v8.0.1

v8.0.0

v7.3.4

v7.3.3

v7.3.2

v7.3.1

v7.3.0

v7.2.0

v7.1.2

v7.1.1

v7.1.0

v7.0.0

v6.1.1

v6.1.0

v6.0.0

v5.10.0

v5.9.0

v5.8.0

v5.7.0

v5.6.0

v5.5.0

v5.4.0

v5.3.1

v5.3.0

v5.2.0

v5.1.1

v5.1.0

v5.0.0

4.0.1

4.0.0

3.1.0

v3.0.2

v3.0.1

v3.0.0

v2.5.1

v2.5.0

v2.4.1

v2.4.0

v2.3.0

v2.2.0

v2.1.0

v2.0.1

v2.0.0

v1.18.0

v1.17.1

v1.17.0

v1.16.1

v1.16.0

v1.15.1

v1.15.0

Labels

No items

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

adam (Adam Wojcieszonek)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/vscode-front-matter#153