You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was a bit confused by the list_lead definition. Why does options default to a hash, when the argument only works with a string?
# works
client.list_leads('name:"Some name"', true)
# does not work
client.list_leads({"name" => "Some name"}, true)
Also, just to be sure, the gem does not support limiting fields, right? Explained on the Close.io documentation page:
Most endpoints support a _fields parameter that lets you specify which fields you require in the response. For example, if you only need ID and display_name when listing Leads, add ?_fields=id,display_name to the URL. This will improve performance of your API calls.
Given how list_leads is implemented I don't think it is possible to pass on that argument.
The text was updated successfully, but these errors were encountered:
Cool gem!
I was a bit confused by the
list_lead
definition. Why does options default to a hash, when the argument only works with a string?Also, just to be sure, the gem does not support limiting fields, right? Explained on the Close.io documentation page:
Given how
list_leads
is implemented I don't think it is possible to pass on that argument.The text was updated successfully, but these errors were encountered: