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

Devel #173

Merged
merged 4 commits into from
Aug 4, 2023
Merged

Devel #173

merged 4 commits into from
Aug 4, 2023

Conversation

bms63
Copy link
Collaborator

@bms63 bms63 commented Jul 25, 2023

Thank you for your Pull Request!

We have developed a Pull Request template to aid you and our reviewers. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the xportr codebase remains robust and consistent.

The scope of {xportr}

{xportr}'s scope is to enable R users to write out submission compliant xpt files that can be delivered to a Health Authority or to downstream validation software programs. We see labels, lengths, types, ordering and formats from a dataset specification object (SDTM and ADaM) as being our primary focus. We also see messaging and warnings to users around applying information from the specification file as a primary focus. Please make sure your Pull Request meets this scope of {xportr}. If your Pull Request moves beyond this scope, please get in touch with the {xportr} team on slack or create an issue to discuss.

Please check off each task box as an acknowledgment that you completed the task. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the devel branch until you have checked off each task.

Changes Description

(descriptions of changes)

Task List

  • The spirit of xportr is met in your Pull Request
  • Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
  • Summary of changes filled out in the above Changes Description. Can be removed or left blank if changes are minor/self-explanatory.
  • Check that your Pull Request is targeting the devel branch, Pull Requests to main should use the Release Pull Request Template
  • Code is formatted according to the tidyverse style guide. Use styler package and functions to style files accordingly.
  • Updated relevant unit tests or have written new unit tests. See our Wiki for conventions used in this package.
  • Creation/updated relevant roxygen headers and examples. See our Wiki for conventions used in this package.
  • Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
  • Run pkgdown::build_site() and check that all affected examples are displayed correctly and that all new/updated functions occur on the "Reference" page.
  • Update NEWS.md if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers)
  • Address any updates needed for vignettes and/or templates
  • Link the issue Development Panel so that it closes after successful merging.
  • Fix merge conflicts
  • Pat yourself on the back for a job well done! Much love to your accomplishment!

@codecov
Copy link

codecov bot commented Jul 25, 2023

Codecov Report

Merging #173 (8e893bc) into main (b9f0c17) will increase coverage by 30.64%.
Report is 450 commits behind head on main.
The diff coverage is 100.00%.

❗ Current head 8e893bc differs from pull request most recent head ffce646. Consider uploading reports for the commit ffce646 to get more accurate results

@@             Coverage Diff              @@
##             main      #173       +/-   ##
============================================
+ Coverage   69.35%   100.00%   +30.64%     
============================================
  Files          10        12        +2     
  Lines         372       580      +208     
============================================
+ Hits          258       580      +322     
+ Misses        114         0      -114     
Files Changed Coverage Δ
R/df_label.R 100.00% <100.00%> (+21.73%) ⬆️
R/format.R 100.00% <100.00%> (+18.75%) ⬆️
R/label.R 100.00% <100.00%> (+21.21%) ⬆️
R/length.R 100.00% <100.00%> (+32.25%) ⬆️
R/messages.R 100.00% <100.00%> (+43.13%) ⬆️
R/metadata.R 100.00% <100.00%> (ø)
R/order.R 100.00% <100.00%> (+18.18%) ⬆️
R/support-test.R 100.00% <100.00%> (ø)
R/type.R 100.00% <100.00%> (+16.21%) ⬆️
R/utils-xportr.R 100.00% <100.00%> (+30.85%) ⬆️
... and 2 more

@bms63 bms63 requested review from EeethB and elimillera August 3, 2023 19:47
@bms63
Copy link
Collaborator Author

bms63 commented Aug 3, 2023

Can one of you approve - I can't reproduce the linter error locally. NOt really concerned.

Copy link
Collaborator

@averissimo averissimo left a comment

Choose a reason for hiding this comment

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

@bms63 I wasn't able to reproduce it either until updating the lintr package, the corrections are in #176

Fix lint errors in `devel` that appear with new version of `{lintr}` 📦
@elimillera elimillera merged commit c0a7cb1 into main Aug 4, 2023
@bms63 bms63 deleted the devel branch November 16, 2023 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants