plopjs/plop

Base path with relative path fails to find templates

Open

#240 opened on Sep 19, 2020

View on GitHub
 (5 comments) (1 reaction) (0 assignees)JavaScript (266 forks)batch import
buggood first issuehelp wanted

Repository metrics

Stars
 (6,845 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Hi. I am using plop to generate a lot of boilerplate for my projects and it works great. Just encountered a scenario where,

THIS WORKS

{
                type: "addMany",
                destination: "./path/to/{{camelCase name}}",
                base: `my/templates`,
                templateFiles: "my/templates/**/*",
                stripExtensions: ["txt"],
                verbose: true,

 }

THIS DOES NOT WORK

{
                type: "addMany",
                destination: "./path/to/{{camelCase name}}",
                base: `./my/templates`,
                templateFiles: "my/templates/**/*",
                stripExtensions: ["txt"],
                verbose: true,

 }

The only difference is the prefix of ./ in the base config and plop is not able to find any files when using that. I am not sure if it is intended but thought i would let you know.

Contributor guide

Research direction
Inspect how the base path is processed in the addMany action, focusing on normalization of relative paths that include './' prefix.
Tech stack
javascript
Domain
tooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Node.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70