We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If I use this js frontmatter in a .md or .njk file, the navigation item works as expected (i.e. url and key are /one and One, respectively):
js
.md
.njk
url
key
/one
One
---js const permalink = "/one/"; const eleventyNavigation = { key: "One", } ---
Similarly, standard frontmatter works:
--- permalink: "/one/" eleventyNavigation: { key: One, } ---
But the same thing in a .webc file doesn't work. key is found, but url is undefined.
.webc
undefined
I've created a fork of the 11ty WebC base, showing the issue. Am I missing something/do I need to treat WebC differently?
It may be a separate issue, but InputPathToUrlTransformPlugin also fails for any WebC templates.
InputPathToUrlTransformPlugin
The text was updated successfully, but these errors were encountered:
No branches or pull requests
If I use this
js
frontmatter in a.md
or.njk
file, the navigation item works as expected (i.e.url
andkey
are/one
andOne
, respectively):Similarly, standard frontmatter works:
But the same thing in a
.webc
file doesn't work.key
is found, buturl
isundefined
.I've created a fork of the 11ty WebC base, showing the issue. Am I missing something/do I need to treat WebC differently?
It may be a separate issue, but
InputPathToUrlTransformPlugin
also fails for any WebC templates.The text was updated successfully, but these errors were encountered: