-
-
Notifications
You must be signed in to change notification settings - Fork 599
Duplicate APIs that differ only in casing #542
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
Comments
Not annoying! |
Fixed. As this looks like Microsoft manually moving API documents around, and doesn't seem to be a widespread problem, so I'll leave it as a manual fix for now. Thanks for raising the issue. |
Amazing, thanks for sorting this. |
@MikeRalphson, a user downstream (httptoolkit/openapi-directory-js#20) has just pointed out that this reappeared at some point, and there are now duplicates with different casing for at least Azure.com/azsadmin-quotas and Azure.com/sql-databaseSecurityAlertPolicies:
I haven't done a proper check for other examples, I suspect there may be more! I'm going to update openapi-directory-js shortly, and I'll see if I can automatically spot & flag those there myself, but it might also be worth finding a way to check them here too if possible. It looks like really these are valid, it's just that they should just be compared case-insensitively so each pair here are treated as specs for the same service, right? |
Thanks! On your last point, you're probably right, I just need to check how much work it's going to be. It's probably come back because I've moved from Linux to a mac. |
Just to confirm here, I have now added some checks on my end to catch this, and I think there are only 3 cases currently with casing issues (as opposed to the Googleapis.com issue in #777) and they're all Azure:
|
Azure.com contains specs for both
sql-databases
andsql-Databases
:It also has specs for both
azsadmin-Quotas
andazsadmin-quotas
:Definitely seems like a mistake, and something that might cause unpredictable behaviour in some environments.
(I'm planning to keep filing minor errors I spot like this, partly just for my reference, but do let me know if it's annoying!)
The text was updated successfully, but these errors were encountered: