-
Notifications
You must be signed in to change notification settings - Fork 14
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
0029 feedback create iso8601 #33
Conversation
There was a bug that could lead `assert_capture_matrix()` to return its output (matrix) with columns out of order. This is now ensured.
This is loosely inspired on https://github.com/tidyverse/readr/blob/main/R/problems.R
One more example about the `problems()` function.
…he date/time components Previously, `create_iso8601()` would not trigger a warning if at least one of the date, time or date-time components parsed successfully. Now it is enough for one single component to fail at parsing for warnings to be triggered. This is following the request: #33 (comment).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks so much @ramiromagno, works like a charm 🙏
Merge branch 'update-links-docs' into 0029_feedback_create_iso8601 # Conflicts: # .github/CONTRIBUTING.md
I have just integrated Adam's recent commits on the hyperlinks' update, and the Links Workflow is passing now 🚀 So only the Test Coverage and the Roxygen workflows fail now: see issue #35. |
Hello @rammprasad and @galachad: Now that all checks are passing, could you review this PR now? |
@galachad, can we please get your blessing before we merge? |
Merge remote-tracking branch 'origin/main' into 0029_feedback_create_iso8601 # Conflicts: # .github/CONTRIBUTING.md
Fixes the NR CMD check NOTE: ❯ checking DESCRIPTION meta-information ... NOTE Malformed Description field: should contain one or more complete sentences.
Thank you for your Pull Request! We have developed this task checklist from the
Development Process
Guide
to help with the final steps of the process. Completing the below tasks helps to
ensure our reviewers can maximize their time on your code as well as making sure
the oak codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task
or check off that it is not relevant to your Pull Request. 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.Request Title (Use Edit button in top-right if you need to update)
tidyverse style guide. Run
styler::style_file()
to style R and Rmd filesconsider realistic data scenarios and edge cases, e.g. empty datasets, errors,
boundary cases etc. - See
Unit Test Guide
fully follow the
deprecation guidance?
and families. Refer to the
categorization of functions to tag appropriate keyword/family.
devtools::document()
so all.Rd
files in theman
folder and theNAMESPACE
file in the project root are updated appropriatelyNEWS.md
if the changes pertain to a user-facing function (i.e. ithas an
@export
tag) or documentation aimed at users (rather than developers)pkgdown::build_site()
and check that all affectedexamples are displayed correctly and that all new functions occur on the "Reference" page.
lintr::lint_package()
R CMD check
locally and address all errors and warnings -devtools::check()