Merged
Conversation
seabbs
approved these changes
Jan 8, 2025
Contributor
seabbs
left a comment
There was a problem hiding this comment.
Nice LGTM. Just needs a news entry
Collaborator
Author
|
Ha I hoped you would let me get away since it's just an internal thing :D I'll add a news item |
This file contains hidden or 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
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.
Description
This PR closes #979.
This PR closes #972 .
This PR fixes the issues above by handling all renaming of columns in
as_forecast_generic(). The code there became a bit more complicated, but on the other hand the individualas_forecast_()functions got simplified to the point that they become almost trivial. In a later PR we could really internalise all the logic intoas_forecast_generic()and only pass in the class name as an arg.Checklist
lintr::lint_package()to check for style issues introduced by my changes.