Skip to content
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

#inDir() fires after generator is setup #565

Closed
eddiemonge opened this issue May 27, 2014 · 4 comments
Closed

#inDir() fires after generator is setup #565

eddiemonge opened this issue May 27, 2014 · 4 comments

Comments

@eddiemonge
Copy link
Member

this means things like this.config.path is set to whatever directory the script is in before changing to the one supplied in .inDir(). This makes testing things like saving config harder. .run() should wait to process entries until after inDir has finished

@SBoudrias
Copy link
Member

Ah! That's the issue, good catch!

@eddiemonge
Copy link
Member Author

issue with something else or this?

@SBoudrias
Copy link
Member

I think there's been a report of a similar bug somewhere. You just pinned the cause :)

blai pushed a commit to blai/generator that referenced this issue May 28, 2014
blai pushed a commit to blai/generator that referenced this issue May 29, 2014
blai pushed a commit to blai/generator that referenced this issue May 29, 2014
… chance to alter

the environment to the a specific way and expect `env` and `generator` reflects such
settings. Also emits `ready` event right before calling `generator.run()` to allow any
last minute operation on the `generator`

fixes yeoman#565
blai pushed a commit to blai/generator that referenced this issue May 30, 2014
… chance to alter

the environment to the a specific way and expect `env` and `generator` reflects such
settings. Also emits `ready` event right before calling `generator.run()` to allow any
last minute operation on the `generator`

fixes yeoman#565
blai pushed a commit to blai/generator that referenced this issue Jun 4, 2014
… a chance to alter

the environment to the a specific way and expect `env` and `generator` reflects such
settings.

- Emits `ready` event right before calling `generator.run()` to allow any
last minute operation on the `generator`

- Deprecating `onEnd`, instead emits 'end' event as `generator.on('end')`

- Implement `withGenerator()` to mock generator dependencies

- accepts optional second parameter in `inDir` as a callback function.

fixes yeoman#564, yeoman#565, yeoman#573
@blai blai mentioned this issue Jun 4, 2014
7 tasks
blai pushed a commit to blai/generator that referenced this issue Jun 4, 2014
… a chance to alter

the environment to the a specific way and expect `env` and `generator` reflects such
settings.

- Emits `ready` event right before calling `generator.run()` to allow any
last minute operation on the `generator`

- Deprecating `onEnd`, instead emits 'end' event as `generator.on('end')`

- Implement `withGenerator()` to mock generator dependencies

- accepts optional second parameter in `inDir` as a callback function.

fixes yeoman#564, yeoman#565, yeoman#573
blai pushed a commit to blai/generator that referenced this issue Jun 4, 2014
… a chance to alter

the environment to the a specific way and expect `env` and `generator` reflects such
settings.

- Emits `ready` event right before calling `generator.run()` to allow any
last minute operation on the `generator`

- Deprecating `onEnd`, instead emits 'end' event as `generator.on('end')`

- Implement `withGenerator()` to mock generator dependencies

- accepts optional second parameter in `inDir` as a callback function.

fixes yeoman#564, yeoman#565, yeoman#573
@SBoudrias
Copy link
Member

Fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants