-
-
Notifications
You must be signed in to change notification settings - Fork 737
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
composeWith sub-generator not mocking as expected #1706
Comments
I'm having the same issue. There's a command that's being run within the sub-generator that should be mocked and therefore not run. |
I have a SO question here outlining the issue. AFAICT, the only answer I've been given, as light on detail as it is, does not work, and worryingly, the user who answered purports to be a contributor to the Yeoman project 😟. |
@wulfgarpro @SBoudrias is one of the core contributors and wrote the sub-generator stuff. |
The problem is that when you composeWith a generator path, it will load that path and ignore the registered generators/mocks. The mock is registered to the environment with the namespace. As far as I can see this is not a bug so I am closing it. |
I'm trying to test my generator, which, using composeWith, relies on a sub-generator (generator-express):
But, I keep getting the following error:
The error, indicating that the sub-generator is still being executed, leads me to believe that the mock is not actually working?
The text was updated successfully, but these errors were encountered: