search for: regardess

...hould never win a conflict, so conflicted checks for use of `.Deprecated()`. This rule is very useful when moving functions from one package to another. For example, many devtools functions were moved to usethis, and conflicted ensures that you always get the non-deprecated version, regardess of package attach order: head(conflict_scout(c("devtools", "usethis"))) #> 26 conflicts: #> * `use_appveyor` : [usethis] #> * `use_build_ignore` : [usethis] #> * `use_code_of_conduct`: [usethis] #> * `us...

...hould never win a conflict, so conflicted checks for use of `.Deprecated()`. This rule is very useful when moving functions from one package to another. For example, many devtools functions were moved to usethis, and conflicted ensures that you always get the non-deprecated version, regardess of package attach order: head(conflict_scout(c("devtools", "usethis"))) #> 26 conflicts: #> * `use_appveyor` : [usethis] #> * `use_build_ignore` : [usethis] #> * `use_code_of_conduct`: [usethis] #> * `use...

...nflict, so conflicted > checks for use of `.Deprecated()`. This rule is very useful when > moving functions from one package to another. For example, many > devtools functions were moved to usethis, and conflicted ensures > that you always get the non-deprecated version, regardess of package > attach order: > I would completely believe this rule is useful for refactoring as you describe, but that is the "same function" case. For an end-user in the "different function same symbol" case it's not at all clear to me that the deprecated function...

...nflict, so conflicted > checks for use of `.Deprecated()`. This rule is very useful when > moving functions from one package to another. For example, many > devtools functions were moved to usethis, and conflicted ensures > that you always get the non-deprecated version, regardess of package > attach order: > > head(conflict_scout(c("devtools", "usethis"))) > #> 26 conflicts: > #> * `use_appveyor` : [usethis] > #> * `use_build_ignore` : [usethis] > #> * `use_code_of_condu...

...ct, so conflicted > checks for use of `.Deprecated()`. This rule is very useful when > moving functions from one package to another. For example, many > devtools functions were moved to usethis, and conflicted ensures > that you always get the non-deprecated version, regardess of package > attach order: > > head(conflict_scout(c("devtools", "usethis"))) > #> 26 conflicts: > #> * `use_appveyor` : [usethis] > #> * `use_build_ignore` : [usethis] > #> * `use_code_o...