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
Support deep coercion for Hash attributes #112
Conversation
@greyblake it looks like you left in a Also, this may be something you're already doing, but make sure you run |
@dkubb, thanks for catching
There defenetly should be a way to find out what code is not covered. Thanks. |
@greyblake yeah, you can run the Most of the output comes from parsing errors in YARD so other than silencing them I don't know if there's anything I can do in yardstick to make them go away. |
# @api public | ||
attr_reader :value_type | ||
|
||
|
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.
It's a tiny point, but there's an extra blank line here.
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.
addressed in 0242d1c
@dkubb To avoid yardstick warnings we can extract module created dynamically into a constant: # Some doc
AttributeEalizer = Equalizer.new(inspect) << :name << :options
include AttributeEalizer |
Issue solnic#112 Issue solnic#98
Yes. Me or @dkubb must find time to do the final review and merge :) I'll work on it when I'm in Kiev next weekend :) conferences == OSS hacking :) On Tuesday, September 25, 2012 at 3:00 PM, Sergey Potapov wrote:
|
Ok. |
@greyblake thanks for that. I just merged it in :) |
Great! Thanks)) |
Issue #98
Here we are.