-
-
Notifications
You must be signed in to change notification settings - Fork 12
Full Attributes for HTMLConverter.convert #99
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
Comments
Unfortunately I'm messing with this part of the codebase as we speak, but fortunately it should make this easier to achieve I believe Also, nitpick, its MDEx v0.2.0, not v2.0 😂 |
Also for posterity, the "attrs" for these functions are the yaml front matter. Its poorly named and part of what I'm changing at the moment. |
Thanks for the note I'll wait for your change. LOL and thanks for the fix re: v0.2. |
mhanberg
added a commit
that referenced
this issue
Oct 10, 2024
This allows you to use dynamic data in your content files if your converter supports it. Closes #99 BREAKING-CHANGE: Posts no longer fallback to the first <h1> tag as the title of the post
NICE!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm experimenting with MDEx 2.0 & expanding liquid tags in the markdown. I can't figure out how to expose the data/site assigns to the
HTMLConverter.convert
function.Firstly I wrote a converter module to handle liquid tags - this seems to work fine:
Secondly I modified the
HTMLConvert
modules to handle liquid tags. This works fine with one problem. The attrs contain the markdown frontmatter variables, but not the site'sdata
orsite
assigns.@mhanberg can you point out how to expose the site/data assigns in the
HTMLConvert
modules? TIAThe text was updated successfully, but these errors were encountered: