plopjs/plop

Custom ActionTypes do not work when bypassing prompts (used with plop.load)

Open

#315 opened on Mar 6, 2022

View on GitHub
 (6 comments) (0 reactions) (0 assignees)JavaScript (6,845 stars) (266 forks)batch import
buggood first issue

Description

Hi everyone,

first of all, thank you for all the great work. Now back to my problem. In my package plop-action-eslint, I try to add tests for the custom type. It works when I cd into the package and run yarn plop but does not when I run yarn plop Template \"Test\". You'll see the screenshots of the issue in my PR https://github.com/natterstefan/plop-action-eslint/pull/1/files here.

What am I missing? You can use my repository to reproduce what I am talking about.

Thanks for your help.

Contributor guide

Tech stack
javascriptnodejs
Domain
clitoolingdeveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Node.jsplop basicscustom action types
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate how plop handles custom action types when prompts are bypassed (using plop.load). Look at the source code for action type registration and prompt bypass logic. Review the screenshots in the linked PR (github.com/natterstefan/plop action eslint/pull/1) to understand the failure mode. Check if there are any existing tests for this scenario.