Skip to content
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

Fuzzy match package recommendations should be case-insensitive #4135

Open
D3MZ opened this issue Jan 14, 2025 · 1 comment
Open

Fuzzy match package recommendations should be case-insensitive #4135

D3MZ opened this issue Jan 14, 2025 · 1 comment

Comments

@D3MZ
Copy link

D3MZ commented Jan 14, 2025

Image

Both HTTP and BSON exist, but the fuzzy match recommendations don't suggest the cased-counterparts.

Depending on your philosophy here, I think it's worthwhile to either:

  1. Install with a warning about the cased version of the package is being installed and will need to be referenced as such.
  2. OR prevent case sensitivity on packages.
  3. OR make fuzzy matching case-insensitive, so packages like HTTP and BSON, will show up when a user tries to install http and json respectively.

I'm making this a feature request because:

  1. It's a risk if you're allowing both http and HTTP to co-exist.
  2. A little annoying to start projects with many packages that have their own unique casing.
  3. Confusing for beginners like myself seeing that "http package doesn't exist". This is because both pip and gem are case-insensitive when downloading packages.
@DilumAluthge
Copy link
Member

Option 3 seems like the best approach here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants