Is this inheritance practice bad (jade)?

Question

css

Hello colleagues.
Now I have the following in my project:
There is a partial:
top-navigation.jade
Another partial
sidebar.jade
is included inside it And top-navigation.jade itself is included in layot.jade, and I add the layout to the pages through extands.
I'm asking this question because I'm having trouble compiling to gulp. Already installed and configured gulp-jade-inheritance. But still gulp refuses to compile the last partial - sidebar.jade. Can it is necessary to refuse such "deep" inheritance, or it is normal practice?
Task

gulp.task('jade', function() {
  gulp.src(path.source.html)
    .pipe(changed('public/', {extension: '.html'}))
    .pipe(jadeInheritance(plugins.jadeInheritance.options))
    .pipe(jade(plugins.jade.options))
    .on('error', handleError)
    .pipe(gulp.dest(path.dest.html))
    .pipe(reload({stream:true}));
});

Answer 1

I would recommend using jade mixins for partials. At least it's convenient + you can pass the parameters. You can see my standard template for a quick site layout.