👋 Thanks for opening this pull request! Can you please run through the following checklist before requesting review (ticking as complete or if not relevant).

• Read our contribution guidelines if you have not already done so.
• If you have altered an existing class please run the tests locally (using devtools::load_all(); devtools::test()) first setting options(testDownload=TRUE, testSource=class-name) and report your findings.
• If you have added a new data class please run the tests locally for that class (using devtools::load_all(); devtools::test()).
• Check your code passes our CI checks and review any style and code coverage warnings.
• Comment with details if unable to get our CI checks to pass or unable to remove all warnings.

Thank you again for the contribution. If making large scale changes consider using our pre-commit hooks (see the contributing guide) to more easily comply with our guidelines.

I imagine this has some conflicts with recent package changes? Should we pause on this for now and or pull the code out elsewhere? It might be worth having a little think about data integrity checks in general (i.e a validate check of a data source separate from "unit" testing etc). It would be nice to increase data specific testing. Same goes for #312.

This PR has been flagged as stale due to lack of activity