Option to limit processing to a specified configuration #104

Merged
merged 1 commit into from Apr 18, 2012

Projects

None yet

2 participants

@sixten
Contributor
sixten commented Apr 17, 2012

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.

@rentzsch rentzsch merged commit 1a86e88 into rentzsch:master Apr 18, 2012
@rentzsch
Owner

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?

@sixten
Contributor
sixten commented Apr 23, 2012

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. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment