cran-comments.md

Test environments (fedregs version 1.0.0)

R CMD check results

The previous version failed because of a breaking change with tidyr::nest and tidyr::unnest (tidyr >= 1.0.0). The code was updated to function as expected with these new changes. There were no ERRORs, WARNINGS, or NOTEs in R 3.6.1 or R-devel on the first 5 systems.

On win-builder (devel) there was 1 ERROR Package required and available but unsuitable version: 'tidyr' This update to fedregs is in response to the update to tidyr, so this should be expected, and I am depending on the improved version.

Corrections/Comments:

Test environments (fedregs version 0.1.1)

R CMD check results

The previous version failed because of a breaking change in the Code of Federal Regulations API. The US Federal Government was shutdown and the maintainer was not able to update code before the package was removed from CRAN. The current CFR API should be stable for the foreseeable future. There were no ERRORs, WARNINGS, or NOTEs.

Corrections/Comments:

Test environments (fedregs version 0.1.0)

R CMD check results

This is the first submission of 'fedregs'. There were no ERRORs, WARNINGs, or NOTEs.

Downstream dependencies

There are no downstream dependencies.

Corrections/Comments:

1) pls omit the redundant " A Package to Facilitate". DONE 2) Is there some reference about the method you can add in the Description field in the form Authors (year) ? NO 3) We see all your examples are wrapped in \dontrun{}, hence nothing get tested. But then you always need to download data, so this part is probably to be accepted as is. This version of the package will need to download the data for each step, so the \dontrun{} is to keep the speed within CRAN checks.



slarge/fedregs documentation built on May 29, 2020, 5:13 p.m.