-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
define expectations around case-sensitivity for coordinates #1169
Comments
Observations for Go coordinatesExample: Source: pkg.go.dev
Example where pkg.go.dev has two packages with different case. From pkg.go.dev perspective, these are different packages. In actuality, they go to the same github repo.
NOTE: I was not able to find either of these in CD. Azure blob storage (always case sensitive)case sensitive - For the example, only has blobs for CosmosDB _id (case sensitive)(can configure a case-insensitive index, but one has not been configured) Finds: with Does NOT Find: with /definitions endpoint (case insensitie)with body:
Both return the exact same definition. The only difference is in the results, the attribute name for each matches the passed in case. partial results:
UI definition (case insensitive)Both URLs go to the same definition page, but the URL is maintained in the case used to open the page.
If you view the Raw Data for both, they are exactly the same, with the coordinates using the lower case version of UI searchCannot test. Using /definitions search (case sensitive)Searching with provider using Searching with provider using |
Description
It is unclear if CD is handling case-sensitivity for coordinates consistently. This issue seeks to define what is expected and evaluate whether that is sufficient. This includes observations about how it is being handled by the various systems and how package managers expect case variations to be handled.
The text was updated successfully, but these errors were encountered: