Scoped configuration about infection HOT 4 CLOSED

If #89 and #79 are implemented, would that resolve this?

from infection.

Well not exactly :) To be exact what has been implemented allow this but at a global level. What I'm actually thinking of is what we currently have but for smaller subsets. For example you could define that the directory src/Domain should be strictly tested so a lot of mutators enabled for it and for another part like src/Infrastructure reduce the strictness so apply a lot less mutators.

Right now this would be doable by applying different configuration files and merge the result sort of. But in any case, I think what we have is good enough for now. I'll re-open the issue with more details when I'll have time to dig deeper into this

from infection.

What if, in addition to 'ignoring' mutators on certain namespaces/methods etc, we have a 'whitelist' option ( or another name), that says: only apply this mutator/profile on these namespescapes/methods?

from infection.

I'm not sure yet tbh. I really prefer to dig into this with a real-life scenario first before going further in what we actually need to make it work :)

from infection.