You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I define a default layout using the _data/layouts.js method described in #380, anything set in the front matter of the layout isn't actually available through the data cascade. Front matter from the template is available, the layout gets applied, but the front matter from the layout is missing.
If I specify the layout directly in the page template, or if I use the subdir/subdir.json method to set a default, the data cascade works as documented and picks up values from the layout's front matter.
For now I've just switched to the subdir.json method, so I've got a workaround.
This is with 11ty 1.0.0.
The text was updated successfully, but these errors were encountered:
Maybe a good news/bad news situation here...
I created a simple repo which should illustrate the issue: https://github.com/pdehaan/11ty-2298 (I hacked the permalink frontmatter so it would write version specific index HTML pages if you wanted to look at the generated www/ files).
I verified in 0.12.1, 1.0.0, 1.0.1-canary.3, and 2.0.0-canary.4 and got the following results:
If I define a default layout using the _data/layouts.js method described in #380, anything set in the front matter of the layout isn't actually available through the data cascade. Front matter from the template is available, the layout gets applied, but the front matter from the layout is missing.
If I specify the layout directly in the page template, or if I use the subdir/subdir.json method to set a default, the data cascade works as documented and picks up values from the layout's front matter.
For now I've just switched to the subdir.json method, so I've got a workaround.
This is with 11ty 1.0.0.
The text was updated successfully, but these errors were encountered: