Flagging this code below here to note that we should avoid hard coding data into our code. Hard-coding data means it is difficult to update if there data changes, individual errors can be introduced and sensitive data might be accidentally added into the code.
I'd recommend either connecting to the SQL server for historic data and calculating or build csv files with the data created with R/SQL code that is stored in the repo. I prefer the second method as it means the data are only generated once save computational time in this case because the historic data are unlikely to change only when an error is spotted and corrected.
Hi @hugo-e-pigott,
Flagging this code below here to note that we should avoid hard coding data into our code. Hard-coding data means it is difficult to update if there data changes, individual errors can be introduced and sensitive data might be accidentally added into the code.
https://github.com/Vanuatu-National-Statistics-Office/vnso-RAP-tradeStats-materials/blob/da269cd5b5c0b41440cf8ee350262a280ad5c542/R/MonthlyReportAndTables/3_buildMonthlyReport.Rmd#L123
I'd recommend either connecting to the SQL server for historic data and calculating or build csv files with the data created with R/SQL code that is stored in the repo. I prefer the second method as it means the data are only generated once save computational time in this case because the historic data are unlikely to change only when an error is spotted and corrected.
Joe