The changes in the ExtensionData design introduced in EnergyModelsBase v0.9.1 and the corresponding adjustment in EnergyModelsGeography v0.11.3 led to some issues with checking that the function mode_data is working for new TransmissionModes.
The core problem is that we require the function mode_data to be present for all TransmissionModes in the new design to create the variables. To avoid breaking changes, we introduced a default approach in which ExtensionData[] is returned in cases in which the field :data is not existing in a TransmissionMode. As a consequence, if a user changes the name for the extension data field without providing a new method for mode_data, it is not caught.
The thought process is to remove the default behavior in EnergyModelsGeography in the next breaking release and then activate the tests related to it again.
The changes in the
ExtensionDatadesign introduced inEnergyModelsBasev0.9.1 and the corresponding adjustment inEnergyModelsGeographyv0.11.3 led to some issues with checking that the functionmode_datais working for newTransmissionModes.The core problem is that we require the function
mode_datato be present for allTransmissionModes in the new design to create the variables. To avoid breaking changes, we introduced a default approach in whichExtensionData[]is returned in cases in which the field:datais not existing in aTransmissionMode. As a consequence, if a user changes the name for the extension data field without providing a new method formode_data, it is not caught.The thought process is to remove the default behavior in
EnergyModelsGeographyin the next breaking release and then activate the tests related to it again.