-
Notifications
You must be signed in to change notification settings - Fork 2
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
read and write updates #46
base: dev
Are you sure you want to change the base?
read and write updates #46
Conversation
@mstackhouse I added the variable metadata argument to write, since this is not on the datasetjson object anymore. I can change the write function if we want to move it back to datasetjson. |
Column metasdata arguments
…e datasetjson object
…file_metadata since these aren't relevant anymore. cleaned up utils.
} | ||
|
||
|
||
set_column_metadata <- function(columns) { |
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.
@nicholas-masel no issue with this as is, but do we this to be a) exported, and if so, b) would we then want the first parameter back to x
to be pipe-compatible.
R/variable_metadata.R
Outdated
# x | ||
} | ||
|
||
#' #' Apply dataframe to itemData attribute |
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.
We should archive / delete tehis
@@ -10,7 +10,7 @@ | |||
#' @examples | |||
#' # Write to character object | |||
#' ds_json <- dataset_json(iris, "IG.IRIS", "IRIS", "Iris", iris_items) | |||
#' js <- write_dataset_json(ds_json) | |||
#' js <- write_dataset_json(ds_json, iris_items) |
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.
I think we can remove this again
|
||
}) | ||
|
||
test_that("JSON can checked from URL", { | ||
fpath <- paste0("file://", normalizePath(test_path("testdata", "ae.json"))) | ||
fpath <- paste0("file://", normalizePath(test_path("testdata", "invalid_dm.json"))) | ||
expect_warning( | ||
err <- validate_dataset_json(fpath), |
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.
Do you think this is valuable and worth the dependency?
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 admiral 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.styler::style_file()
to style R and Rmd filesdevtools::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. it has an@export
tag) or documentation aimed at users (rather than developers)pkgdown::build_site()
and check that all affected examples 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()