-
Notifications
You must be signed in to change notification settings - Fork 24
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
rm gwasglue2 functions #57
Conversation
@explodecomputer I rm all mentions of |
In last week's commits @explodecomputer used an anonymous function in zzz.R on lin 53 Line 53 in 83f47dd
Anonymous functions were only introduced in R 4.1.0 . So either we need to fix that back to a standard function call or bump the version of R in the DESCRIPTION to 4.1.0. My preference is to use a standard function here. |
Please remove the version check on startup. This is because once on CRAN you/we should bump the version of the package in the GitHub repo to a development version number, i.e., ending .9000 . If you leave the version check in it will trigger every time and people will be confused because they have the CRAN version, so why should they need to then go and install the GitHub version. |
Great news it seems CRAN accepted a resubmission Gib https://cran.r-project.org/package=ieugwasr well done! But is the version on master the version that was accepted? I'm guessing maybe not as the accepted CRAN version says 0.2.0 and master says 0.1.8. So we need to get the accepted version onto master. And add the appropriate git tag and do a GitHub release. Is it up to commit 72ed9e9 that is the CRAN version? Then you can add commits subsequent to the accepted version into this PR (or an additional PR), as the package build is still broken on R 4.0.5 as I noted above so that simple fix needs adding (or the R version needs bumping). |
Congratulations @explodecomputer! |
* Fixing issues with tests failing when server load is an issue
Many thanks @ritarasteiro @remlapmot I've fixed the anonymous function issue now also thanks for spotting that! And codecov seems to have started working again, I don't know why. |
Great. But I would still prefer it if we could remove the version check on package load for packages that are on CRAN (it's fair enough to do it in packages just on GitHub). Look what happens when someone installs this from CRAN - they instantly get the message telling them to reinstall from GitHub - not a great user experience. install.packages('ieugwasr')
#>
#> The downloaded binary packages are in
#> /var/folders/kt/7xskrb1n4_x2jkd9lt0rhybh0000gp/T//RtmpCmFnaW/downloaded_packages
library(ieugwasr)
#>
#> Warning:
#> You are running an old version of the ieugwasr package.
#> This version: 0.2.2
#> Latest version: 0.2.2-9000
#> Please consider updating using remotes::install_github('MRCIEU/ieugwasr')
#> OpenGWAS updates:
#> Date: 2024-03-07
#> [>] There is exceptional load on the OpenGWAS servers.
#> [>] Urgent infrastructure development being performed.
#> [>] See local options for analysis: https://mrcieu.github.io/gwasvcf/. Created on 2024-04-03 with reprex v2.1.0 (To update packages we should teach people the standard methods, i.e., that they should run |
Also for packages on CRAN for the pkgdown site it's good to turn on pkgdown's development mode https://pkgdown.r-lib.org/reference/build_site.html?q=mode#development-mode. To do this to _pkgdown.yml simply add these 2 lines development:
mode: auto Then the main site will be for versions with release numbers, and there will be a dev subdirectoty in the site with the pages for the development version. |
To show you what you get with development mode set to
done automagically by pkgdown 🪄 |
Start preparing resubmission.
gwasglue2