Open lkldev opened 2 years ago
We think that there are some cases where the user may want case sensitive packages as abbreviations/acronyms may make a difference. As such, we chose that the packages should be case sensitive.
Team chose [response.Rejected
]
Reason for disagreement: Whether the user wants abbreviations/acronyms, I believe package names should still be case insensitive. For instance, if the user wants to add a package AIA, it does not make sense to have two package names AIA
and aia
, which may confuse the user and they may end up giving the wrong package to the client.
Steps to reproduce
run addp i/basic package d/
Expected
Package not created as basic package exist (same name)
Actual
Package was created
Screenshots
Since package name are the unique identifier, it seems like package name should be case insensitive. Also, for a fast typist, it will be easier not to consider the case sensitivity here.