change hubdocs URL to hubverse.io

.github/CODE_OF_CONDUCT.md

@@ -38,11 +38,11 @@ Examples of unacceptable behavior include:
 
 ## Enforcement Responsibilities
 
-Community leaders are responsible for clarifying our standards of acceptable behavior. Enforcement is the responsibility of the [Code of Conduct Committee](https://hubdocs.readthedocs.io/en/latest/coc/committee.html), who will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. 
+Community leaders are responsible for clarifying our standards of acceptable behavior. Enforcement is the responsibility of the [Code of Conduct Committee](https://hubverse.io/en/latest/coc/committee.html), who will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. 
 
-Instances of abusive, harassing, or otherwise unacceptable behavior [may be reported to any member of the Code of Conduct Committee](https://hubdocs.readthedocs.io/en/latest/coc/committee.html). All complaints will be reviewed and investigated promptly and fairly. 
+Instances of abusive, harassing, or otherwise unacceptable behavior [may be reported to any member of the Code of Conduct Committee](https://hubverse.io/en/latest/coc/committee.html). All complaints will be reviewed and investigated promptly and fairly. 
 
-The Code of Conduct Committee will use the [Enforcement Manual](https://hubdocs.readthedocs.io/en/latest/coc/enforcement-manual.html) in determining the consequences for any action they deem in violation of this Code of Conduct. All community leaders and Code of Conduct Committee members are obligated to respect the privacy and security of the reporter of any incident.
+The Code of Conduct Committee will use the [Enforcement Manual](https://hubverse.io/en/latest/coc/enforcement-manual.html) in determining the consequences for any action they deem in violation of this Code of Conduct. All community leaders and Code of Conduct Committee members are obligated to respect the privacy and security of the reporter of any incident.
 
 
 ## Scope

.github/CONTRIBUTING.md

@@ -2,7 +2,7 @@
 
 This outlines how to propose a change to `hubEvals`. 
 For more general info about contributing to this, and other hubverse packages, please see the
-[**hubverse contributing guide**](https://hubdocs.readthedocs.io/en/latest/overview/contribute.html). 
+[**hubverse contributing guide**](https://hubverse.io/en/latest/overview/contribute.html). 
 
 You can fix typos, spelling mistakes, or grammatical errors in the documentation directly using the GitHub web interface, as long as the changes are made in the _source_ file. 
 This generally means you'll need to edit [roxygen2 comments](https://roxygen2.r-lib.org/articles/roxygen2.html) in an `.R`, not a `.Rd` file. 

README.Rmd

@@ -52,4 +52,4 @@ Please note that the hubEvals package is released with a [Contributor Code of Co
 ## Contributing
 
 Interested in contributing back to the open-source Hubverse project?
-Learn more about how to [get involved in the Hubverse Community](https://hubdocs.readthedocs.io/en/latest/overview/contribute.html) or [how to contribute to the hubEvals package](.github/CONTRIBUTING.md).
+Learn more about how to [get involved in the Hubverse Community](https://hubverse.io/en/latest/overview/contribute.html) or [how to contribute to the hubEvals package](.github/CONTRIBUTING.md).

README.md

@@ -48,5 +48,5 @@ project, you agree to abide by its terms.
 
 Interested in contributing back to the open-source Hubverse project?
 Learn more about how to [get involved in the Hubverse
-Community](https://hubdocs.readthedocs.io/en/latest/overview/contribute.html)
+Community](https://hubverse.io/en/latest/overview/contribute.html)
 or [how to contribute to the hubEvals package](.github/CONTRIBUTING.md).

tests/testthat/test-transform_point_model_out.R

@@ -61,7 +61,7 @@ test_that("model_out_tbl_1 output is valid", {
     test_path("testdata/exp_forecast_1.csv")
   )
   class(exp_forecast) <- c("forecast", "forecast_point", "data.table", "data.frame")
-  expect_equal(act_forecast, exp_forecast)
+  expect_equal(act_forecast, exp_forecast, ignore_attr = "class")
 })
 
 test_that("test target_data has observation column", {
@@ -98,7 +98,7 @@ test_that("model_out_tbl_1 columns are valid", {
   exp_forecast <- utils::read.csv(test_path("testdata/exp_forecast_1.csv")) |>
     dplyr::rename(loc = location, trgt = target, date = target_end_date)
   class(exp_forecast) <- c("forecast", "forecast_point", "data.table", "data.frame")
-  expect_equal(act_forecast, exp_forecast)
+  expect_equal(act_forecast, exp_forecast, ignore_attr = "class")
 
   # Error when missing any of: model_id, output_type, output_type_id, value
   expect_error(
@@ -188,5 +188,5 @@ test_that("hubExamples data set is transformed correctly", {
       target_end_date = as.Date(target_end_date, "%Y-%m-%d")
     )
   class(exp_forecast) <- c("forecast", "forecast_point", "data.table", "data.frame")
-  expect_equal(act_forecast, exp_forecast)
+  expect_equal(act_forecast, exp_forecast, ignore_attr = "class")
 })

tests/testthat/test-transform_quantile_model_out.R

@@ -23,7 +23,7 @@ test_that("model_out_tbl_1 output is valid", {
 
   exp_forecast <- utils::read.csv(test_path("testdata/exp_forecast_2.csv"))
   class(exp_forecast) <- c("forecast", "forecast_quantile", "data.table", "data.frame")
-  expect_equal(act_forecast, exp_forecast)
+  expect_equal(act_forecast, exp_forecast, ignore_attr = "class")
 })
 
 test_that("test target_data has observation column", {
@@ -62,7 +62,7 @@ test_that("model_out_tbl_1 columns are valid", {
   ) |>
     dplyr::rename(loc = location, trgt = target, date = target_end_date)
   class(exp_forecast) <- c("forecast", "forecast_quantile", "data.table", "data.frame")
-  expect_equal(act_forecast, exp_forecast)
+  expect_equal(act_forecast, exp_forecast, ignore_attr = "class")
 
   # Error when missing any of: model_id, output_type, output_type_id, value
   expect_error(
@@ -147,5 +147,5 @@ test_that("hubExamples data set is transformed correctly", {
       target_end_date = as.Date(target_end_date, "%Y-%m-%d")
     )
   class(exp_forecast) <- c("forecast", "forecast_quantile", "data.table", "data.frame")
-  expect_equal(act_forecast, exp_forecast)
+  expect_equal(act_forecast, exp_forecast, ignore_attr = "class")
 })