Non-ascii package names not supported

[JKamsker]

Are you experiencing an issue with...

shields.io

🐞 Description

NCòdexSDK: https://img.shields.io/nuget/v/NC%C3%B2dexSDK.svg?logo=nuget

Reports as not found.
Nuget link: https://www.nuget.org/packages/NC%C3%B2dexSDK/0.0.1

🔗 Link to the badge

https://img.shields.io/nuget/v/NC%C3%B2dexSDK.svg?logo=nuget

💡 Possible Solution

No idea, probably happens because of the funny ó in the middle which i used to circumvent the stupid global ban of the word Codex in nuget package names.

[github-actions]

Badge tested using npm run badge https://img.shields.io/nuget/v/NC%C3%B2dex
Output is available here

[jNullj]

Hey @JKamsker
I took a look at the logs and tested ascii only example as well.
It looks like we might have an upstream issue with the API we are using.

Notice how we get 0 hits from the search. I tried multiple ways to call it but could not get a hit on the name of that package.

Request  🏹 
 https://azuresearch-usnc.nuget.org/query?q=packageid%3Anc%25C3%25B2dex&prerelease=true&semVerLevel=2
{
  "headers": {
    "Accept": "application/json"
  }
}
 Response status code  🎯 
 200
 Response JSON (before validation)  🎯
{
  '@context': {
    '@vocab': 'http://schema.nuget.org/schema#',
    '@base': 'https://api.nuget.org/v3/registration5-gz-semver2/'
  },
  totalHits: 0,
  data: []
}
 Response after validation  🛁
{ data: [] }
 Handled error  🙅 
 NotFound: Not Found: package not found