not escaped accentuated characters about linkedin HOT 6 CLOSED

Hey Flowfeeler,

Are you able to provide a failing test case so I can look into this further?

Thanks,

Josh

from linkedin.

I'm having the same problem with some accentuated characters. For example, the search for "André" gives the following issue:

result = linkedin.search(:keywords => 'André', :count => 1)

/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/uri/generic.rb:512:in check_query': bad component(expected query component): count=1&keywords=André (URI::InvalidComponentError) from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/uri/generic.rb:526:inquery='
from /Library/Ruby/Gems/1.8/gems/linkedin-0.1.7/lib/linked_in/client.rb:190:in to_uri' from /Library/Ruby/Gems/1.8/gems/linkedin-0.1.7/lib/linked_in/client.rb:103:insearch'
from linkedin_test.rb:10

from linkedin.

CGI.escape seems to solve this issue:

result = linkedin.search(:keywords => CGI.escape('André'), :count => 1)

I think a good solution would be add this escaping automatically in the gem instead of in the parameters. What do you think?

Regards,
Renato

from linkedin.

Hi Renatosnrg,

I have just pushed a fix to master which uses URI.escape which fixes the utf8 issues you were having.

If there is a good reason to change to CGI vs URI, please let me know and I will look into it.

I hope to release a new patch version soon, until then please feel free to use the git repo in your Gemfile.

Thanks,

Josh

from linkedin.

Thanks a lot!

Renato

from linkedin.

Sorry about that, I have been out traveling for a while, I had monkey patched that on my side but forgot about it. I'm glad it has been fixed :)

from linkedin.