Twitter expects parentheses to be encoded. We are experiencing tweet failures when the text contains parentheses.
I tested the search scenario this was changed for and Twitter properly decodes the encoded parentheses so this shouldn't cause a regression for the v2 search endpoint
This PR fixes a regression introduced in https://github.com/DanielaSfregola/twitter4s/pull/411
Twitter expects parentheses to be encoded. We are experiencing tweet failures when the text contains parentheses.
I tested the search scenario this was changed for and Twitter properly decodes the encoded parentheses so this shouldn't cause a regression for the v2 search endpoint