🚧 What needs to be done
It was noted recently that an activated configuration contains a codes array and a code_system_sets array, which both contain information about codes required for refinement. These arrays contain the same code information, however, code_system_sets contains objects that have a little more info about a code (its name and the system it belongs to).
There is no reason to duplicate this information. It likely makes the most sense to ensure that codes does not make it into the active.json file that is created upon activation.
🤔 Why it needs to be done
TES version 6.0.0 introduced significantly more codes, causing activation files to balloon in size. This is a very basic first step we can take to alleviate this issue at least a bit.
🏗️ Acceptance Criteria
⚙️ Technical Notes
N/A
🚧 What needs to be done
It was noted recently that an activated configuration contains a
codesarray and acode_system_setsarray, which both contain information about codes required for refinement. These arrays contain the same code information, however,code_system_setscontains objects that have a little more info about a code (its name and the system it belongs to).There is no reason to duplicate this information. It likely makes the most sense to ensure that
codesdoes not make it into theactive.jsonfile that is created upon activation.🤔 Why it needs to be done
TES version 6.0.0 introduced significantly more codes, causing activation files to balloon in size. This is a very basic first step we can take to alleviate this issue at least a bit.
🏗️ Acceptance Criteria
codesarray is no longer written to theactive.jsonfile upon activationactive.json⚙️ Technical Notes
N/A