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

support displaying column counts at higher levels in column structure #856

Closed
wants to merge 2 commits into from
Closed

Conversation

gmbecker
Copy link
Collaborator

@gmbecker gmbecker commented Apr 12, 2024

clean lint, includes tests, doesn't include updates to vignette(s)

Comment on lines +249 to +251
## likely unneeded now because it happens in splitvec_to_coltree
## which is called during coltree construction above
## TODO remove me
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if it is not run at all anymore we can already remove it

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we remove it?

#' Get or set column count for a facet in column space
#'
#' @inheritParams gen_args
#' @param path character. This path must end on a
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#' @param path character. This path must end on a
#' @param path (`string`)\cr this path must end on a

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is incorrect. A string, in as much as it exists at all (which, again, in R it doesnt), has length one, whereas a path is a character vector of any length.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will admit I forgot to put the weird new stuff around it though...

@gmbecker
Copy link
Collaborator Author

Also, I don't really have any idea whats going on with the spell checker, it appears to be flagging files that this PR doesn't change (e.g., tt_as_flextable.Rd)

I can't easily use pre-commit in my fork because the hooks have been updated from 0.4.0 to 0.4.2 and it won't even run the checks unless you update the pre-commit hook yaml file, but then it won't match what is in the insightsengineering repo... @cicdguy any advice on that?

@cicdguy
Copy link
Contributor

cicdguy commented Apr 15, 2024

Also, I don't really have any idea whats going on with the spell checker, it appears to be flagging files that this PR doesn't change (e.g., tt_as_flextable.Rd)

I can't easily use pre-commit in my fork because the hooks have been updated from 0.4.0 to 0.4.2 and it won't even run the checks unless you update the pre-commit hook yaml file, but then it won't match what is in the insightsengineering repo... @cicdguy any advice on that?

Ok investigatiNg this.

@gmbecker
Copy link
Collaborator Author

Also, I don't really have any idea whats going on with the spell checker, it appears to be flagging files that this PR doesn't change (e.g., tt_as_flextable.Rd)
I can't easily use pre-commit in my fork because the hooks have been updated from 0.4.0 to 0.4.2 and it won't even run the checks unless you update the pre-commit hook yaml file, but then it won't match what is in the insightsengineering repo... @cicdguy any advice on that?

Ok investigatiNg this.

Shot in the dark, if it is running spell check on the full diffs instead of the additions, it could be catching things that were removed. That could explain why it always complains so much and about seemingly random things, but it wouldn't explain complaining about files I didn't touch at all, so I dunno

Copy link
Contributor

@Melkiades Melkiades left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gmbecker @shajoezhu I think before this one we should merge the other outstanding PRs from Gabe. As soon as those are in we can review this PR more in detail. Should we start to get #819 passing the tests?

#' Set visibility of column counts for a group of sibling facets
#'
#' @inheritParams gen_args
#' @param path character. The path *to the parent of the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#' @param path character. The path *to the parent of the
#' @param path (`character`)\cr the path *to the parent of the

Comment on lines +2448 to +2449
#' desired siblings*. The last element in the path should
#' be a split name.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#' desired siblings*. The last element in the path should
#' be a split name.
#' desired siblings*. The last element in the path should
#' be a split name.

#' Get or set column count for a facet in column space
#'
#' @inheritParams gen_args
#' @param path character. This path must end on a
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#' @param path character. This path must end on a
#' @param path (`character`)\cr this path must end on a

@gmbecker gmbecker marked this pull request as draft April 23, 2024 18:09
@gmbecker
Copy link
Collaborator Author

Converted to draft because it turns out this requires a large rework how cbinding works befcause the current way of cbinding does not result in column structure where all elements are path-addressable.

I have this working in the combined branch we are working off of at J&J but I haven't cherrypicked the changes to put them into this PR yet. I will do so (or it won't matter if we get the truetype stuff merged in first)

@gmbecker
Copy link
Collaborator Author

@gmbecker @shajoezhu I think before this one we should merge the other outstanding PRs from Gabe. As soon as those are in we can review this PR more in detail. Should we start to get #819 passing the tests?

#819 is subsumed by the truetype font PR, which was derailed by the large scale doc changes causing tons of conflicts. The corresponding formatters PR exists, and I'll work on getting the rtables one up, but that is the one we should use

@gmbecker
Copy link
Collaborator Author

Closing this PR and will open another one after #865 is merged in (I have a bundled branch we are doing our work with that has both features so I'll merge that into a new branch after the first PR settles)

@gmbecker gmbecker closed this May 21, 2024
@github-actions github-actions bot locked and limited conversation to collaborators May 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants