Skip to content

Fix Position docs #3223

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

Merged
merged 1 commit into from
Apr 11, 2019
Merged

Fix Position docs #3223

merged 1 commit into from
Apr 11, 2019

Conversation

flying-sheep
Copy link
Contributor

The function signature is compute_panel(self, data, params, scales) -> data

The function signature is `compute_panel(self, data, params, scales) -> data`
@thomasp85 thomasp85 merged commit 105203f into tidyverse:master Apr 11, 2019
@thomasp85
Copy link
Member

Thanks

@flying-sheep flying-sheep deleted the patch-1 branch April 11, 2019 12:55
@yutannihilation
Copy link
Member

FYI: you needed to run devtools::document() to re-generated the docs.

yutannihilation added a commit to yutannihilation/ggplot2 that referenced this pull request Apr 12, 2019
yutannihilation added a commit that referenced this pull request Apr 13, 2019
@flying-sheep
Copy link
Contributor Author

Sure, but for one-off fixes using the GitHub UI, that’s not feasible.

Maybe there should be a bot that recognizes PRs that change #' doc comments where no .Rd changes happened and adds them in commits to (or after) that PR.

@batpigandme
Copy link
Contributor

Given that there can be several functions inside a single .R file that export to different .Rds, and roxygen's parsing of tags, this would be non-trivial. I'm not sure where a Feature Request for something like this world go. Maintainers with write access can always document for you, if it's a problem.

@flying-sheep
Copy link
Contributor Author

flying-sheep commented Apr 15, 2019

The idea is simpler: If any line in a .R file starting with #' is changed, but no file with an .Rd extension is changed in the same PR, the bot checks out the changes, runs devtools::document() and checks if that would produce any changes. If it does, it either commits them directly to the existing PR or creates another PR depending on it.

Maintainers with write access can always document for you, if it's a problem.

I can do that too, but why not automate something as boring as that?

@batpigandme
Copy link
Contributor

I like the idea. It deserves to live somewhere other than ggplot2 PR comments.

@flying-sheep
Copy link
Contributor Author

What are you thinking? Sadly roxygen2 doesn’t live in an organization where we could propose that.

@hadley
Copy link
Member

hadley commented Apr 15, 2019

It's already in the pipeline.

@lock
Copy link

lock bot commented Oct 12, 2019

This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/

@lock lock bot locked and limited conversation to collaborators Oct 12, 2019
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.

5 participants