feat: Support for extending pug templates using relative paths #83
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here's another. When extending a Pug template from a relative path, Pug compiler requires a filename attribute to be given in the compile() method options.
Apparently the filename has to be the full path to the file being compiled, which is something that can't be achieved via Jest configuration since it's common to all tests. But as the full path of the file being processed is available in the template compiler, it's easy to pass it to the Pug compiler in order to make extending from relative paths work correctly.