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

allow self-referencing for YAML-blocks in md files #2

Closed
trenkert opened this issue Feb 7, 2018 · 4 comments
Closed

allow self-referencing for YAML-blocks in md files #2

trenkert opened this issue Feb 7, 2018 · 4 comments

Comments

@trenkert
Copy link

trenkert commented Feb 7, 2018

right now, pandoc-mustache depends on an external yaml-file from which to draw its variables. Would it be possible to include a function that - if no
mustache: ./external_variables.yaml
has been specified, mustache reads the yaml-block of the input file and expects references to variables in the body text?

something like

---
date: 1.1.1970
---

The day of {{date}} does not lie in the future

?

@rriemann
Copy link

rriemann commented May 3, 2018

This would be an interesting feature. 👍

@michaelstepner
Copy link
Owner

This is an interesting idea. I'm not sure off hand if it's in the spirit of the Mustache templating spec, but it does seem useful. I'd welcome more discussion. I'd potentially merge a pull request that implements this.

I've pasted the contributing section from the README below.

Contributing

Project Status: Inactive

This code is not being actively developed. It was created to fulfill my pandoc writing needs, and the current feature set is adequate for me.

If you have a feature request, it is unlikely that I will be able to implement it for you. You can create an issue to generate discussion. If you implement a feature, you can file pull request and I will review it eventually, as time permits. If you're interested in making major additions to the code, I'd be happy to welcome a new maintainer to the project.

@rriemann
Copy link

rriemann commented Mar 1, 2020

Has this been closed as wont-fix or has this been implemented?

@copart
Copy link

copart commented Apr 21, 2021

I implemented what I believe this issue was requesting.

Submitted as a pull request:
#11

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

No branches or pull requests

4 participants