Deprecate epi_recipe() in favour of recipe()
#370
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* missing rlang prefix * max(NULL, date) produces an integer, tests fail
Merge branch 'dev' into 330-epi_recipe # Conflicts: # DESCRIPTION # NAMESPACE # R/autoplot.R # R/epi_keys.R # R/epi_recipe.R # R/layer_add_forecast_date.R # R/layer_add_target_date.R # R/layer_cdc_flatline_quantiles.R # R/layer_threshold_preds.R # R/layers.R # R/reexports-tidymodels.R # R/step_training_window.R # man/autoplot-epipred.Rd # man/layer_add_forecast_date.Rd # man/layer_add_target_date.Rd # man/layer_cdc_flatline_quantiles.Rd # man/layer_threshold.Rd # man/recipe.epi_df.Rd # man/reexports.Rd # man/step_training_window.Rd # man/update.layer.Rd # tests/testthat/test-key_colnames.R # tests/testthat/test-population_scaling.R # vignettes/update.Rmd
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
Please:
dajmcdon.
DESCRIPTIONandNEWS.md.Always increment the patch version number (the third number), unless you are
making a release PR from dev to main, in which case increment the minor
version number (the second number).
(backwards-incompatible changes to the documented interface) are noted.
Collect the changes under the next release number (e.g. if you are on
0.7.2, then write your changes under the 0.8 heading).
Change explanations for reviewer
This is a major (breaking?) change. Do not merge until we are ready for a major version update.
Magic GitHub syntax to mark associated Issue(s) as resolved when this is merged into the default branch
epi_recipe()#330