Skip to content
This repository has been archived by the owner on May 28, 2019. It is now read-only.

Detect bad monkeypatching #164

Open
aslakhellesoy opened this issue Feb 23, 2012 · 0 comments
Open

Detect bad monkeypatching #164

aslakhellesoy opened this issue Feb 23, 2012 · 0 comments

Comments

@aslakhellesoy
Copy link
Contributor

See cucumber/cucumber-rails#198 and #76

Gherkin should fail immediately if someone has accidentally monkey-patched Object with methods that conflict with our own methods.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant