Open EvaJanouskova opened 5 months ago
We could perhaps also change the names of such RFs so that the names contain a notation indicating that these files are generated by a script, so that it is clear at a glance (e.g. prefix _
, or suffix _gen
).
It's a good idea. We could possibly add a note to the 'README.md' about the ResourceFiles being 'read only' (unless you're generating them from a script), or we could this in a 'README.txt' file in resources/healthsystem
Could we have a test for Resource Files generated by a script (ie, not created manually) to assure no one has manually made a change in that RF?
I had no idea a RF was generated by a script, so I made all the changes manually, it was even merged to master creating so a bit mess. But if it would cause a test to fail, we might have known.