Add ability for more complex searchTerm

[Villarrealized]

Changed encodeURIComponent to encodeURI to allow for forward slashes within the search term. This allows for deeper browsing/searching which was not possible before as any forward slashes would have been lost to conversion.

// Before
encodeURIComponent('Blues/B.B. King')
// -> Blues%2FB.B.%20King
// With change
encodeURI('Blues/B.B. King')
// -> Blues/B.B.%20King

[Villarrealized]

This could probably be more simply accomplished by leaving the current code as-is but changing from encodeURIComponent to encodeURI which preserves additional slashes.

I think I like that better as it is more flexible and doesn’t add additional parameters to the function and accomplishes the same thing.

What do you think?

[phoenixrising87]

Yes, I also like this idea more. Keeps the code simpler and more flexible.

[Villarrealized]

Great, I updated the PR with the new changes.

[bencevans]

:tada: This PR is included in version 1.9.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: