You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when building a virtual submodule, if the name already exists, the existing one is simply updated with the built indicators.
This means that when re-building a module after having removed a few indicators from the yaml, these indicators still appear in the update module and thus are iterated over with iter_indicators. We should have an option to "reset" the module, without having to restart the python kernel.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Generic Issue
Currently, when building a virtual submodule, if the name already exists, the existing one is simply updated with the built indicators.
This means that when re-building a module after having removed a few indicators from the yaml, these indicators still appear in the update module and thus are iterated over with
iter_indicators
. We should have an option to "reset" the module, without having to restart the python kernel.Code of Conduct
The text was updated successfully, but these errors were encountered: