-
Notifications
You must be signed in to change notification settings - Fork 214
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
Allow multiple aliases for the same option flag #2751
Comments
At the moment, I prefer to have exactly one alias for one option flag. I personally find it confusing to have multiple aliases, as it indicates a difference that actually does not exist. However, the Julia wrapper seems to allow for multiple aliases. Hm... Is there a "Pythonic rule" regarding this issue or decision? I agree that it is confusing to have different aliases between GMT and PyGMT, and we should try to focus on consistency. In case we decide on multiple aliases, how is this realized in the examples? Do we want to define a "preferred" or "recommended" alias, which is then used in all examples? Or do we have to update the examples to mention all available aliases? If we used different aliases across the examples for the same thing, I feel that at least new users would definitely get confused. |
I think multiple aliases cause more trouble than benefits. Closing the issue and feel free to reopen the issue if you don't argee. |
See GenericMappingTools/gmt#7923 for context.
In PyGMT,
-j
is aliased todistcal
, but upstream GMT suggestsmetric
.We need to discuss if we want to allow multiple aliases or deprecate
distcal
tometric
.The text was updated successfully, but these errors were encountered: