You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encountered the following issue whereby the config did not show an error (which makes sense) and the UI shows This collection has no entries yet. My collection settings were:
The UX bug (as I would call it) is that Sveltia did not return content in the UI nor inform the user as to why there was no content.
I assumed this is because Sveltia tried to parse the entire file as yaml but since it was a .md + frontmatter file, Sveltia failed silently. Converting the files .yaml and updating extension: "yaml" worked, but incorrect for my SSG.
Changing the value to format: "frontmatter" makes all the data correctly show, as expected 😄
Suggestions
Show user friendly message in UI
## Oops
We found content, but were unable to display it.
Please make sure your settings and files are correct:
folder: "content/widgets/"
extension: "md"
format: yaml
Console log a parsing error (if there is?) such as this so there's a clue.
Relates to #17 but I think is discreet enough to warrant a separate issue and path to resolution.
The text was updated successfully, but these errors were encountered:
I encountered the following issue whereby the config did not show an error (which makes sense) and the UI shows
This collection has no entries yet.
My collection settings were:The UX bug (as I would call it) is that Sveltia did not return content in the UI nor inform the user as to why there was no content.
I assumed this is because Sveltia tried to parse the entire file as
yaml
but since it was a.md + frontmatter
file, Sveltia failed silently. Converting the files.yaml
and updatingextension: "yaml"
worked, but incorrect for my SSG.Changing the value to
format: "frontmatter"
makes all the data correctly show, as expected 😄Suggestions
Relates to #17 but I think is discreet enough to warrant a separate issue and path to resolution.
The text was updated successfully, but these errors were encountered: