Help
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Copilot Lvl 2
Message 1 of 5

graphql api resource query is case sensitive

Solved! Go to Solution.

Hi

The graphql api resource query is case sensitive. When I try to query a object using url, for example:

https://github.com/by2hit will not work, but https://github.com/BY2HIT is working.

 

this will not work:

{
    resource(url: "https://github.com/by2hit") {
    __typename
}

 

this will work:

 

{
    resource(url: "https://github.com/BY2HIT") {
    __typename
}

 

On the other hand, type both the lowercased or the upper cased url in a browser can visit the same page.

4 Replies
Commander Lvl 1
Message 2 of 5

Re: graphql api resource query is case sensitive

Hi @myrfy001,

This post was moved to a different board that fits your topic of discussion a bit better. This means you’ll get better engagement on your post, and it keeps our Community organized so users can more easily find information.

As you’ll notice, your Topic is now in the Project Development Help board. No action is needed on your part; you can continue the conversation as normal here.

Let me know if you have any other questions or if I can help with anything else.

Cheers!

Community Manager
Message 3 of 5

Re: graphql api resource query is case sensitive

Hi @myrfy001,

 

Our apologies, we incorrectly moved this to the Project Development Help and Advice Board when it should be in the How to use Git and GitHub forum since I believe you are reporting issues with GitHub's GraphQL API. I have moved this post to the How to use Git and GitHub board where you can continue this discussion further.

 

Thanks!

Ground Controller Lvl 1
Message 4 of 5

Re: graphql api resource query is case sensitive

where to find the topic been moved by you. how to make case-insensitive query?

Solution
Commander Lvl 3
Message 5 of 5

Re: graphql api resource query is case sensitive

This may be due to the fact that the API uses different systems than the browser. It's best to just keep it case-sensitive on your end - nothing can go wrong then.


- Mark