Closed mikestopcontinues closed 6 years ago
@mikestopcontinues Hi, thanks for your feedback, I'll check it out soon.
Thanks, @GitScrum! You rock!
@mikestopcontinues Can you show your current posthtml
config and the plugin order ?
Sure!
posthtml([
extend({root}),
modules({root}),
include({root}),
expressions(),
]);
Now you need set extend options plugins
when call expressions
posthtml([
extend({root, plugins: [expressions()]}),
modules({root}),
include({root}),
expressions(),
]);
Ok, thanks!
@mikestopcontinues wait publish in npm )
Does posthtml-extend
(not too familiar with it 😛 ) not also extend the tree
(AST), so posthtml-expressions
should normally work if it is used after posthtml-extend
? We use a custom walk
{Function}
in posthtml-expressions
atm, maybe there is something lost during interpolation ?
@mikestopcontinues Done! enjoy, and close this issue if all good.
Thanks!
Problem
posthtml-extend
updates the tree to be contained within the extended page. For some reason, this breaksposthtml-expressions
. But it would be awesome to both use the plugins together, as well as use expressions logic in the extended template.Reproduction
Two different issues:
Expressions work so long as you don't try to extend the current template.