-
-
Notifications
You must be signed in to change notification settings - Fork 162
Move more pin-caching logic from DocMap to PinCache #1064
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
base: master
Are you sure you want to change the base?
Conversation
To avoid merge conflicts and contributors having to deal with non-intuitive RuboCop todo changes: * Lock down development versions of RuboCop and plugins so that unrelated PRs aren't affected by newly implemented RuboCop rules. * Exclude rule entirely if more than 5 files violate it today, so that PRs are less likely to cause todo file changes unless they are specifically targeted at cleanup. * Clarify guidance on RuboCop todo file in CI error message. * Fix to hopefully ensure guidance always appears in CI error message.
f82c5f8 to
f632481
Compare
|
|
||
| new_pin.docstring.add_tag(tag) | ||
| redefine_return_type new_pin, tag | ||
| new_pin.reset_generated! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This fixes an existing bug, where not only are we not always calling reset_generated! on pins (only when return_type is overridden), and we don't reset the parameters.
As a result, params overloading would only work if #inspect had not been called on the pin before it was overridden, which is bad news for debugging.
See #1066 for the spec behind it; on this branch it fails because some debug logging was added and we're exercising debug logging in specs.
Changes in logic: