mirror of
https://github.com/estruyf/vscode-front-matter.git
synced 2026-11-03 09:02:19 +01:00
Feedback: Metadata section vs. content types in split-file configuration #406
Assignees
adam (Adam Wojcieszonek)
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: adam/vscode-front-matter#406
Reference in new issue
Block a user
I am not sure if this is a bug or a misconfiguration, because in the past weeks I migrated my older config setup to the current state of configuration options (thank you for split config files!).
I uploaded the current state in this commit.
It appears that in my current state Frontmatter does NOT fully recognize my content types. It ignores preview images (defined in the default content type) and i have to add "type: blog" (not the default type) to my frontmatter to show the preview image in the dashboard.
I would expect the default content type to take over, even without the frontmatter
type: contenttypeline. It does, partly, but not with the article image. Content types blog and default are configured identical and the preview image is located in the resource field group.It also shows a weird notice in the sidebar metadata section:
and THEN it shows the fields properly configured by type.
Of the three grey buttons, the first two add their changes to the
frontmatter.jsonfile, NOT my split file config in.frontmatter/taxonomy/contenttypes/*.json. The last button, select content type, shows for a split second a vscode selector popup (like CTRL+SHIFT+P) that is without selections.So, my assumption is, that either I have something configured wrong, or that there is maybe a bug that does not treat the content type 100% separated with splitfiles.
After CTRL+SHIFT+P > Reload Window instead of the Dashboard the install routine pops up, asking for content folders. I guess the pagefolder config is also ignored at certain points.
Same issue here.
@yolpsoftware can you give me more information to start reproducing the issue? I believe @davidsneighbour has already figured this out.
@estruyf sorry I do not remember under what circumstances this has happened. I wanted to try some things out to solve it, or collect more information, but then the problem somehow disappeared.
If it happens again, I'll let you know and I'll provide more information.
Thank you @yolpsoftware, will close the issue for now.
Sidenote: I forgot I opened this issue and it was on my side. I had made changes to the local .frontmatter directory/config and my commit-hook setup stashed uncommitted changes when I did git commits on unrelated things. This "triggered" Frontmatter a bit because the config changed twice (into stash, out of stash), which was too fast for Frontmatter.