-
Notifications
You must be signed in to change notification settings - Fork 34
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
Method whitelist support #183
Comments
I often find myself in a similar situation - I would like to allow only part of the library, a single package, etc... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Often I find myself in a situation where an update to a library drags in a new evil method, and I only discover it after the fact. It would be nice if new methods were treated as suspicious by default.
The syntax I was thinking of was something like:
Allowing people to call
fail()
still while also saying that any other calls toAssertions
' static methods are not OK.This way, when a new method appears, it's automatically blocked, and someone can come and discuss why they think they need it.
The text was updated successfully, but these errors were encountered: