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.
This is so sub-generators (or a collection of similarly-authored generators) can depend on shared data if needed... It relies on a module already in the dependency tree (dependency of a dependency) and is a small addition that enables a powerful subset style of generating, so I see no harm done.
Say for instance, I have
foo
, withfoo:bar
andfoo:qux
that both render different files that requirename
... If we run these at the same time:You can prompt for the data one time (both generators
foo:bar
andfoo:qux
):Yet both generators can still retrieve the name later, with
this.env.shared.get('name')
, without having to reprompt the user.The module I used,
es6-map
, was already in the dep tree, so I'm just reusing it here in a small implementation.Closes yeoman/yo#416