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
Not sure why, but kapitan/inputs/base.py iterates on input_paths and not on the comp_obj directly.
With the changes introduced on #979, not all compile objects will have input_paths.
A workaround was introduced here to deal with these specific compile objects without input_paths
Aim of this issue is to investigate why we iterate on input_paths and not directly on comp_obj. If possible / feasible, change code to iterate on comp_obj to simplify the code.
Suggested by @MatteoVoges on #979 (comment)
Not sure why, but kapitan/inputs/base.py iterates on
input_paths
and not on thecomp_obj
directly.With the changes introduced on #979, not all compile objects will have
input_paths
.A workaround was introduced here to deal with these specific compile objects without
input_paths
Aim of this issue is to investigate why we iterate on
input_paths
and not directly oncomp_obj
. If possible / feasible, change code to iterate oncomp_obj
to simplify the code.@ramaro may have more context on this.
The text was updated successfully, but these errors were encountered: