Issue #427: Fix error in set_forecast_unit()
that occurs when input is not a data.table
#487
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.
Fixes #427
set_forecast_unit()
currently fails when the input is adata.frame()
instead of adata.table()
. This PR hotfixes the issue by making sure by callingas.data.table()
on the input.There exists also a more complete fix including tests and more thorough input checks in #437 that have already been reviewed and merged into the development branch. It would have been more ideal to target that PR to main instead of develop, but given that has already happened I think it is best to make a quick fix here. I ran the tests from the already reviewed PR here as well to make sure everything is working as expected, but didn't replicate them to avoid further merge conflicts due to variable names changing between main and dev.
Not ideal, apologies, will target main with future fixes like this one.