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

Allow overriding default processor configuration on a per-group basis. #214

Open
rlubke opened this issue Dec 18, 2014 · 1 comment
Open
Assignees
Milestone

Comments

@rlubke
Copy link

rlubke commented Dec 18, 2014

There may be cases where certain processors are very specific to a group that they deal with. In these cases, it would be nice to be able to override the default processor configuration and provide a specific configuration for a group.

This could also be a general optimization of the processor pipeline. Consider the case where one group does less processing, but another group is only interested in merging static content. The static content group has no need for less processing, so being able to assign the less processor to the groups that need it only provides a small runtime benefit (if you're using WRO dynamically vs at build time).

@alexo alexo self-assigned this Jan 5, 2015
@alexo
Copy link
Owner

alexo commented Jan 5, 2015

This is an interesting feature and it worth adding it. Thanks for reporting.

@alexo alexo added this to the 1.7.8 milestone Jan 5, 2015
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