You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Contributors Guide in the section Code Style:
When wrapping a new alias, use an underscore to separate words bridged by vowels (aeiou), such as no_skip and z_only. Do not use an underscore to separate words bridged only by consonants, such as distcalc, and crossprofile. This convention is not applied by the code checking tools, but the PyGMT maintainers will comment on any pull requests as needed.
However, some aliases seem not to follow this convention. For example:
pygmt.Figure.plot(): straight_line (A) , error_bar (E), nodata (d)
Following the convention, they should be straigthline, errorbar , no_data
I think that the aliases that do not follow this convention were added to PyGMT before the convention was established. For context, the idea of a convention to ensure consistency for alias names was first suggested in #1190 (comment) and added in #1256.
In the Contributors Guide in the section Code Style:
However, some aliases seem not to follow this convention. For example:
pygmt.Figure.plot()
:straight_line
(A
) ,error_bar
(E
),nodata
(d
)Following the convention, they should be
straigthline
,errorbar
,no_data
pygmt.Figure.rose()
:vector_params
(M
)Should be
vectorparams
.Please note: This is primarily meant as a general question for understanding, rather than a request for renaming these aliases. 😉
The text was updated successfully, but these errors were encountered: