Issues with Search REST API: Special Characters Handling

[Le-Caignec]

What happened?

Hello,

I am currently using the Octokit library to interact with the GitHub Search REST API, and I am facing to an issue that is impacting my ability to use it effectively:

.Handling of Special Characters: Queries that include certain special characters do not execute as expected. For example, the query containing return ( fails, whereas return( (without a space before the parenthesis) succeeds. I attempted to resolve this issue using encodeURI, as recommended in some discussions on GitHub, but it seems this workaround does not apply effectively when using Octokit to interact with the search API.

Here is an example of a failing query:

const query = 'return (';
const results = await octokit.rest.search.code({
  q: query
});

And a succeeding one:

const query = 'return( ';
const results = await octokit.rest.search.code({
  q: query
});

Could you please provide guidance on how to handle these issues? Are there any recommended practices for managing long queries and special characters specifically through Octokit? Any help would be greatly appreciated as these limitations are hindering my usage of the API for larger, more complex code searches.

Thank you for your assistance.

Versions

Node: v20
Octokit: 3.1.2

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀