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

Strict YAML validation collides with existing lua filters for Pandoc #4139

Closed
4 tasks
bcdavasconcelos opened this issue Jan 28, 2023 · 2 comments
Closed
4 tasks
Labels
support a request for support

Comments

@bcdavasconcelos
Copy link

Bug description

The field bibliography now must be validated as a string, but existing filters for Pandoc sometimes use other types. Example:

bibliography:
  primary: test/primary.bib
  secondary: test/secondary.bib

This is the case of the multi bib filter. Please see: pandoc-ext/multibib#1

Is there any way to bypass this validation?

Thank you.

Checklist

  • Please include a minimal, fully reproducible example in a single .qmd file? Please provide the whole file rather than the snippet you believe is causing the issue.
  • Please format your issue so it is easier for us to read the bug report.
  • Please document the RStudio IDE version you're running (if applicable), by providing the value displayed in the "About RStudio" main menu dialog?
  • Please document the operating system you're running. If on Linux, please provide the specific distribution.
@bcdavasconcelos bcdavasconcelos added the bug Something isn't working label Jan 28, 2023
@cscheid
Copy link
Collaborator

cscheid commented Jan 29, 2023

You can add validate-yaml: false to your front matter.

This isn't a bug, though - YAML validation is too important for our users, and since Lua filters can access arbitrary metadata, there's no other alternative for us. Perhaps you could consider changing the way the filter works by accessing multibib from a separate field.

@cscheid cscheid closed this as completed Jan 29, 2023
@cscheid cscheid removed the bug Something isn't working label Jan 29, 2023
@bcdavasconcelos
Copy link
Author

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support a request for support
Projects
None yet
Development

No branches or pull requests

3 participants