Skip to content
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

Consistency of arguments across packages, in particular by, group and group_by. #404

Closed
9 of 10 tasks
strengejacke opened this issue May 15, 2024 · 12 comments
Closed
9 of 10 tasks
Labels
Code Style 👩‍💻 Core Packages 📦 Discussion and planning about core packages of easystats Corporate Design / PR 💅

Comments

@strengejacke
Copy link
Member

strengejacke commented May 15, 2024

We have

  • insight::export_table(group_by)
  • datawizard::data_partition(group)
  • datawizard::data_tabulate(by)
  • datawizard::means_by_group(group)
  • report::report_sample(group_by)

to name a few. I think we should just use one of the three verbs to indicate grouping, to be more consistent across our easystats packages. What would you suggest?

@strengejacke strengejacke added Core Packages 📦 Discussion and planning about core packages of easystats Corporate Design / PR 💅 Code Style 👩‍💻 labels May 15, 2024
@DominiqueMakowski
Copy link
Member

And we sometimes have at as well...

I think I like by, it's concise + it's also in-line with the recent tidyverse evolution .by

@bwiernik
Copy link
Contributor

And we sometimes have at as well...

I think I like by, it's concise + it's also in-line with the recent tidyverse evolution .by

And with marginaleffects and aggregate()

@strengejacke
Copy link
Member Author

In parameters::model_parameters(), should we also rename keep and drop into select and exclude? These argument do not select variables, but regression coefficients, but their intention is similar: to select a subset of data. WDYT?

@DominiqueMakowski
Copy link
Member

I'm not sure, I have the feeling that there should be distinct arguments for columns and for rows

@strengejacke
Copy link
Member Author

ok, makes sense. Better for me, so I don't need to touch this ;-)

strengejacke added a commit to easystats/insight that referenced this issue May 16, 2024
* easystats/easystats#404

* fix data_grid

* fix split_by

* fix

* Update test-marginaleffects.R

* fix

* lintr
etiennebacher added a commit to easystats/datawizard that referenced this issue May 18, 2024
* easystats/easystats#404

* update snapshots

* lintr, comments

* fix demean()

* fix means_by_group

* fix

* update news

* fix rescale_weights

* silence tests

* Update NEWS.md

Co-authored-by: Etienne Bacher <52219252+etiennebacher@users.noreply.github.com>

* deprecation warnings

* use insight remotes

* Update NEWS.md

Co-authored-by: Etienne Bacher <52219252+etiennebacher@users.noreply.github.com>

* Also address #265

* update docs

* update docs and tests

* Update extract_column_names.R

* update readme

* trigger CI

* revert commits related to aliases

* version

* news

* other remnants

* fix

* do not use devel pkgdown

* lintr

* same

---------

Co-authored-by: Etienne Bacher <52219252+etiennebacher@users.noreply.github.com>
@strengejacke
Copy link
Member Author

What about bayestestR::estimate_density()? There's also an at argument.

@bwiernik
Copy link
Contributor

bwiernik commented May 19, 2024

What about bayestestR::estimate_density()? There's also an at argument.

Probably worth changing this one. Oddly enough, looks like group_by is already there and currently deprecated?

@DominiqueMakowski
Copy link
Member

Probably worth changing this one

yup

looks like group_by

We had group_by first, then deprecated in favour of at, and now back to by 😅

@strengejacke
Copy link
Member Author

@DominiqueMakowski and then for modelbased, we rename all ats into bys, too, right?

@DominiqueMakowski
Copy link
Member

Yes

@strengejacke
Copy link
Member Author

What about visualization_matrix()? 🙈

@strengejacke
Copy link
Member Author

Ah, that's only in modelbased. I confused it with visualization_recipe().

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Code Style 👩‍💻 Core Packages 📦 Discussion and planning about core packages of easystats Corporate Design / PR 💅
Projects
None yet
Development

No branches or pull requests

3 participants