I like seeing this into the module, and nice idea on the reflection approach.
Why would you not recommend not to use this on production? I see it more potentially useful on production/test environments because it let non-developers (qa, client services, etc.) now that certain configs are actually overridden.
Just wondering if you see a potential harm on the module or performance.
Fixed
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I've added to the project page the issue is using reflection to change a class method from protected to public, and using reflection is typically not recommended for production environments/code.
Automatically closed - issue fixed for 2 weeks with no activity.