Issue: VSCode issues shows `path` not allowed in frontMatter.data.files

[davidsneighbour]

Latest version.

Describe the bug
Working on my configuration file in VSCode I see a yellow underline in the path-property of the following code sample:

{
  "$schema": "https://frontmatter.codes/frontmatter.schema.json",
  "frontMatter.data.files": [
    {
      "id": "all-sponsors",
      "path": "[[workspace]]/kollitsch/music.toml",
      "type": "sponsors"
    }
  ],
  "frontMatter.data.folders": [],
  "frontMatter.data.types": [
    {
      "id": "sponsors",
      "title": "Sponsors",
      "fileType": "json",
      "labelField": "name",
      "schema": {
        "title": "Sponsors",
        "type": "object",
        "required": [
          "name",
          "url"
        ],
        "properties": {
          "name": {
            "type": "string",
            "title": "Name"
          },
          "url": {
            "type": "string",
            "title": "URL"
          },
          "description": {
            "type": "string",
            "title": "Description"
          }
        }
      }
    }
  ]
}

The overlay says: "Property path is not allowed.". The documentation of that feature includes a path property: https://frontmatter.codes/docs/dashboard#re-using-a-data-type-for-files-or-folders

Either the docs or the schema used to parse the config has an issue here.

[davidsneighbour]

I see the same issue in other files, so maybe I should add some in-depth details:

The following json:

{
  "$schema": "https://frontmatter.codes/frontmatter.schema.json",
  "frontMatter.taxonomy.fieldGroups": [
    {
      "id": "author",
      "labelField": "name",
      "fields": [
        {
          "title": "Author Name",
          "name": "name",
          "type": "string",
          "single": true
        },
        {
          "title": "Social link",
          "name": "social",
          "type": "string",
          "single": true
        }
      ]
    },
  ],
}

leads to the same issue with labelField.

I have structured my configuration into a subfolder that has a watch job on changes and recreates the frontmatter.json on change. The errors/warning come up in the single files, not the resulting frontmatter.json. But from how I understand the $schema property this should not impede these subfiles? Also, other properties (fields, id, etc) are not complained about.

If you want a sample, have a look at my website repo: https://github.com/davidsneighbour/kollitsch.dev

• clone it
• run npm install, cook a coffee, it takes a bit, sorry
• check for the vscode issue reports in assets/config/frontmatter/
  • partials/dashboard-data.json
  • partials/fieldgroups.json
• run the job to create frontmatter.json via npm run build:frontmatter

[estruyf]

Either the docs or the schema used to parse the config has an issue here.

This was an issue with the documentation. I have fixed it. The path property should have been file.

"frontMatter.data.files": [
  {
    "title": "All sponsors",
    "id": "all-sponsors",
    "file": "[[workspace]]/kollitsch/music.toml",
    "type": "sponsors"
  }
]

[estruyf]

Leads to the same issue with labelField.

Also, an issue that slipped into the documentation. The frontMatter.taxonomy.fieldGroups setting only needs the id and fields properties. By updating the documentation, I found a bug in the schema, which will be fixed in version 7.3.1.

[estruyf]

The 7.3.1 release is published which should fix the (unseen) issue.

Thanks, @davidsneighbour for mentioning the documentation issues. It is very much appreciated!

[estruyf]

Linking this to #356