adam/vscode-front-matter
1
0 Fork 0
mirror of https://github.com/estruyf/vscode-front-matter.git synced 2026-10-30 23:41:57 +01:00
Code Issues 77 Packages Projects Releases Wiki Activity

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

New Issue
Closed
opened 2026-10-05 02:37:05 +02:00 by adam · 5 comments
adam commented 2026-10-05 02:37:05 +02:00
Owner
Copy link
Copy source

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.

20220526-20:51:02-Selection-001

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: ```json { "$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. ![20220526-20:51:02-Selection-001](https://user-images.githubusercontent.com/83281/170501200-1979d439-5322-47d7-90d8-3d9b84488b26.png) <!-- github-sync-id:1249602363 -->
adam closed this issue 2026-10-05 02:37:05 +02:00
adam commented 2026-10-05 02:37:06 +02:00
Author
Owner
Copy link
Copy source

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
I see the same issue in other files, so maybe I should add some in-depth details: The following json: ```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` <!-- github-comment-id:1138613076 -->
adam commented 2026-10-05 02:37:06 +02:00
Author
Owner
Copy link
Copy source

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"
  }
]
> 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`. ```json "frontMatter.data.files": [ { "title": "All sponsors", "id": "all-sponsors", "file": "[[workspace]]/kollitsch/music.toml", "type": "sponsors" } ] ``` <!-- github-comment-id:1138772857 -->
adam commented 2026-10-05 02:37:07 +02:00
Author
Owner
Copy link
Copy source

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.

> 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. <!-- github-comment-id:1138789917 -->
adam commented 2026-10-05 02:37:08 +02:00
Author
Owner
Copy link
Copy source

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!

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! <!-- github-comment-id:1138805896 -->
adam commented 2026-10-05 02:37:09 +02:00
Author
Owner
Copy link
Copy source

Linking this to #356

Linking this to #356 <!-- github-comment-id:1156574056 -->
Sign in to join this conversation.
No Branch/Tag Specified
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
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/vscode-front-matter#273