Fixed issue with .Renviron file as requested by reviewer.

CRAN-SUBMISSION

@@ -1,3 +1,3 @@
 Version: 1.0.0
-Date: 2024-02-01 06:50:20 UTC
-SHA: 5812e42484b4d2586fe7122f9724f2e0fbcec698
+Date: 2024-02-02 04:29:49 UTC
+SHA: 16e8099d0af53baa187225d9bc33efad76e1cbca

cran-comments.md

@@ -1,5 +1,14 @@
-## R CMD check results
+## Resubmission 3 Feb 2024
+This is a resubmission. In this version I have:
+
+* Fixed issue with .Renviron file in vignette to comply with CRAN's policies. 
+
+## Resubmission 1 Feb 2024
+This is a resubmission. In this version I have:
 
+* Fixed issue with tests that require a secret token to make an API call
+
+## R CMD check results
 0 errors | 0 warnings | 1 note
 
 * This is a new release.

vignettes/get-started.Rmd

@@ -45,19 +45,19 @@ Keep in mind that if you close your R session or you re-start it, then you'll ne
 ### b. Using an environment variable 
 For a more persistent method that can be used across different projects, set up your token as environment variable. To do this, you first need to load the `usethis` package. 
 
-```{r, message=FALSE}
+```{r eval=FALSE, message=FALSE}
 library(usethis)
 usethis::edit_r_environ()
 ```
 
 This will open your `.Reviron` file. Place your token here and named it `TIMEGPT_TOKEN`. 
 
-```{r}
+```{r eval=FALSE}
 # Inside the .Renviron file 
 TIMEGPT_TOKEN="paste your token here"
 ```
 
-You'll need to restart R for changes to take effect. 
+You'll need to restart R for changes to take effect. Keep in mind that modifying the `.Renviron` file affects all of your R sessions, so if you're not comfortable with this, set your token using the `nixtla_set_token` function. 
 
 ### Validate your token 
 If you want to validate your token, call `nixtla_validate_token`.