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
I don't really have a solution but I'm still not happy with the naming of our external facing functions. Currently there is:
diffdf_issuerows
diffdf_has_issue
I think the diffdf_ prefix is a bit clunky and long. The original idea was to make functions easy to search for on the auto complete mirroring what was done with str_ in stringr and fct_ in forcats. However I realise now all those prefixed functions all relate to specific operations (i.e. all functions related to manipulating strings however there are functions in each of those packages that don't have the prefix as they have other purposes i.e. regex, boundary & fixed
I'm wondering if we should just drop the diffdf prefix (or reduce to just df_?) or find another name ?
The text was updated successfully, but these errors were encountered:
@kieranjmartin ,
I don't really have a solution but I'm still not happy with the naming of our external facing functions. Currently there is:
I think the
diffdf_
prefix is a bit clunky and long. The original idea was to make functions easy to search for on the auto complete mirroring what was done withstr_
in stringr andfct_
in forcats. However I realise now all those prefixed functions all relate to specific operations (i.e. all functions related to manipulating strings however there are functions in each of those packages that don't have the prefix as they have other purposes i.e.regex
,boundary
&fixed
I'm wondering if we should just drop the diffdf prefix (or reduce to just
df_
?) or find another name ?The text was updated successfully, but these errors were encountered: