we need a YML version of the cookiecutter state to regenerate the project if easydata changes.
The old implementation of this wasn't robust against the easydata remo name changing. This should be better.
It ignores the local cookiecutter data and instead uses the generated .easydata.json to generate the YML equivalent
we need a YML version of the cookiecutter state to regenerate the project if easydata changes. The old implementation of this wasn't robust against the easydata remo name changing. This should be better. It ignores the local cookiecutter data and instead uses the generated
.easydata.jsonto generate the YML equivalent