-
-
Notifications
You must be signed in to change notification settings - Fork 242
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
nanoc 4.11.1 introduces breaking change by making compiled_content include the layout #1412
Comments
Yikes — that is definitely a bug. Will investigate. |
@DivineDominion I’m not able to reproduce the problem you described. Could you create a zip of |
@DivineDominion Are you still experiencing this issue? |
This is not an isolated issue, as I just saw the same issue come in: https://groups.google.com/forum/#!topic/nanoc/pbHOJ3T6wiY |
While finding the fix wasn't that bad, I find it pretty hard to create a test project that crashes. I stopped a while ago but will try to squeeze in time this week to figure this out. |
I am now able to reproduce the problem, and am working on a fix. |
Here is a fix: #1421 I am struggling to write a regression test for it, though. |
Good you found the culprit! I ran into it in another project just last week but couldn't trim it down to a simple example :/ |
I upgraded my project from 4.11.0 to 4.11.2 and noticed a weird glitch: the full-text post previews included the layout again.
Turns out that between 4.11.0 and 4.11.1,
#compiled_content
changed and now returns a cached representation with the layout already added. I found that a call tocompiled_content(snapshot: :pre)
makes it look as expected.So fixing this was pretty easy, I just wanted to let you know that this is a change at all so you might add it to the release notes.
I couldn't reproduce this in a vanilla project with v4.11.1, though. Maybe it's because the affected items are references in
preprocess
? If you aren't aware of this change and don't have a hunch what's going on and want me to investigate, I can try different configurations @ddfreyneThe text was updated successfully, but these errors were encountered: