-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Rename group
/group_by
arguments into by
#502
Conversation
group
/group_by
arguments into by
hm, this error seems to be new, but unrelated to this PR. Why does this encoding-error suddenly occur? https://github.com/easystats/datawizard/actions/runs/9109670481/job/25043053199?pr=502 |
It might be due to an |
Co-authored-by: Etienne Bacher <52219252+etiennebacher@users.noreply.github.com>
We have some aliases, we should think about when to remove them?
|
Yes, we could also address #265 at the same time |
Co-authored-by: Etienne Bacher <52219252+etiennebacher@users.noreply.github.com>
Sorry @strengejacke I meant that we could address the text aliases you mentioned and the aliases mentioned in #265 at the same time but in another PR so that we keep this one strictly about renaming args. Sorry for the confusion 😬 |
I hope we don't need to add |
@etiennebacher Why do we have this error for the selection-syntax vignette now? |
@strengejacke have you seen this? |
Yeah, there are quite some files that have been changed... 🤣 But I think it's ok. |
I'm too unfamiliar with git to know how to split commits into separate PRs... 😬 |
I'd really like to keep those separated so that we can point to a clear PR if necessary later, I can try to split this into two PRs a bit later |
Actually, this PR can be merged. I'm not sure it's worth the effort splitting this PR (I just saw, in VSCode, I can add a new branch from the commit where I changed the aliases and then reset this PR to the commit before - should I do this? - but I don't think there's much benefit) The only remaining mystery is the issue in the vignette:
Not sure why this should suddenly fail. |
If you talk about #503 I think it also includes the changes for the
I can reproduce this warning locally with this branch but not with I will try to split this PR this weekend if it's fine for you, or are you in a hurry for this one? |
No, no hurry. |
@strengejacke I fixed the error in the vignette here: b8ac8ea. FYI those instructions were helpful to know how to move the latest N commits to a new branch (still took some manual tweaking though)
|
We have three different test failures but all the rest is green (??):
=> I'm merging |
easystats/easystats#404