As the amount of data grows in this repository, developing on v3 and deploying PR previews will continue to get slower (once we stop vendoring ood). Consider implementing a companion repository to ood, ood-fixtures, which has the same structure as ood, but only contains a small, fixed set of fixture data, sufficient to exercise the website. Ood-fixtures could be used in development and PR builds, while ood could be used in production deploys. Any changes to types would have to be duplicated in ood and ood-fixtures, but I expect the vast majority of changes to be data additions.
The fixture generation functions and the shell script to update ood-fixtures could reside in ood.
As the amount of data grows in this repository, developing on v3 and deploying PR previews will continue to get slower (once we stop vendoring ood). Consider implementing a companion repository to ood, ood-fixtures, which has the same structure as ood, but only contains a small, fixed set of fixture data, sufficient to exercise the website. Ood-fixtures could be used in development and PR builds, while ood could be used in production deploys. Any changes to types would have to be duplicated in ood and ood-fixtures, but I expect the vast majority of changes to be data additions.
The fixture generation functions and the shell script to update ood-fixtures could reside in ood.