Option to limit processing to a specified configuration #104
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rentzsch
added a commit
that referenced
this pull request
Apr 18, 2012
[NEW] Option to limit processing to a specified configuration. (Sixten Otto)
|
Hey Sixten, At first I thought your patch was too specific to be brought into the mainline, but I checked your implementation and it's beautiful and have no problems with rolling it in. Thanks! Aside: Interesting name, what's it's historical background? |
|
Thank you for such a great tool! The name is Swedish, as I understand it, but comes to me by a long a twisty road. :-) |
ddrccw
pushed a commit
to ddrccw/mogenerator
that referenced
this pull request
Jan 20, 2014
[NEW] Option to limit processing to a specified configuration. (Sixten Otto)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I'm running into a situation in a current project where I'm splitting up my model into configurations that will live in separate stores, and it would be useful to process each set of entities with different templates/options. This really just necessitated surfacing an additional option, and then passing it through to the method that gathers the set of entities for processing. (Or, at least, it seemed so; hopefully, I haven't missed some subtleties.)
In the hopes that this might be useful to others, here are my changes.