Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue: YAMLParseError in beta V10.1.8599652 #794

Closed
Digital-Grinnell opened this issue Apr 10, 2024 · 8 comments
Closed

Issue: YAMLParseError in beta V10.1.8599652 #794

Digital-Grinnell opened this issue Apr 10, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@Digital-Grinnell
Copy link

Describe the bug
I was running the beta version and upon update to v10.1.8599652 I started getting "YAMLParseError" messages whenever I opened or had my scripts process any .md with a leading "---" YAML frontmatter marker. Removing the "---" did remove the error, but naturally broke my Markdown.

To Reproduce

  1. Enable beta v10.1.8599652
  2. Open any .md file with YAML frontmatter and an opening '---' line
  3. See the error

Expected behavior
A '---' opening line before the YAML frontmatter is normal and necessary. But if I remove it the syntax error goes away, but leaves my Markdown unuseable. Likewise, if I disable the beta version and switch to the production release (v10.0.2 in my case) the error is no longer present.

Desktop

  • OS: MacOS v12.7.4 or Ubuntu 22.04 LTS
  • Browser: Firefox

Additional Context
Note that I have a Python script run from a FM button and that script is also broken by this bug. The script parses each .md file in my content folder presumably in a similar manner as the VSCode editor does. With the beta version enabled the script no longer works, but it also returns no errors. After switching to the production version all is well again.

@Digital-Grinnell Digital-Grinnell added the bug Something isn't working label Apr 10, 2024
@estruyf
Copy link
Owner

estruyf commented Apr 10, 2024

Hi @Digital-Grinnell, thank you for opening the issue. Can you test out other BETA versions? The version you've mentioned only included an HTML class fix, and I can't seem to reproduce the issue. Looking for a clue why it would occur.

@estruyf
Copy link
Owner

estruyf commented Apr 10, 2024

Could you provide me with some sample content on which you have the issue?

@Digital-Grinnell
Copy link
Author

Digital-Grinnell commented Apr 10, 2024 via email

@davidsneighbour
Copy link

davidsneighbour commented Apr 10, 2024

Do you maybe have the YAML extension installed? I am also experiencing weird YAML errors, but in other files (for instance, template files), where the YAML parser cites frontmatter issues in a content file (not the current file loaded). Going into that content file and then saving it silences the error for a bit, until it finds another content file to complain about.

I thought this might be a YAML plugin issue, not a Frontmatter plugin issue.

Latest Beta version, also for the past two days.

@estruyf
Copy link
Owner

estruyf commented Apr 10, 2024

I found the issue. It was an experiment for #792, but as it was still in testing, I have reverted that change. The new beta should fix it.

@Digital-Grinnell
Copy link
Author

Digital-Grinnell commented Apr 10, 2024 via email

@davidsneighbour
Copy link

I found the issue. It was an experiment for #792, but as it was still in testing, I have reverted that change. The new beta should fix it.

My errors disappeared after this update.

@estruyf
Copy link
Owner

estruyf commented Apr 10, 2024

Thanks @davidsneighbour for verifying

@estruyf estruyf closed this as completed Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants