-
Notifications
You must be signed in to change notification settings - Fork 252
Bug fixes to 0.9.0 #168
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
Bug fixes to 0.9.0 #168
Conversation
* Connection#search now does more graceful nil-checking in its ensure clause, reducing cryptic crash messages * Filter class methods should now be able to gracefully accept numeric literals as filter rhs values
right.to_s | ||
else | ||
raise ArgumentError, "Did not know how to convert argument \"#{right}\" into the rhs of an LDAP filter" | ||
end |
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.
I'd be comfortable with always calling right.to_s.gsub
instead of introducing conditional branching.
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.
Also, add a simple test to make sure this works! :)
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.
Fixed in b133b31
Thanks for the bugfixes @WoodsBagotAndreMarquesLee! Really appreciate you taking the time and expending the effort to help out. I notice that this PR is open against the |
@WoodsBagotAndreMarquesLee hey there, any chance you could rebase this off of master and submit as a new PR? I can't accept this against the |
Superseded by #184 |
…nescape Rebase #168: Connection#unescape handles numerics, #search guards against nil queued_reads
…numeric-unescape Rebase ruby-ldap#168: Connection#unescape handles numerics, #search guards against nil queued_reads
Hey, I just fixed up a couple of the little issues I had when I tried to use your gem out-of-the-box. For what it's worth, it's entirely possible that I only encountered the nil-checking bug because one of my co-workers was messing around with our LDAP server while I was composing and testing my search query, it might not be a problem when working with an operational server.
Implemented a couple of bug fixes: