Closed liamhuber closed 5 days ago
Coverage variation | Diff coverage |
---|---|
:white_check_mark: +0.04% (target: -1.00%) | :white_check_mark: 100.00% |
:rocket: Don’t miss a bit, follow what’s new on Codacy.
Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more
Files with Coverage Reduction | New Missed Lines | % | ||
---|---|---|---|---|
nodes/for_loop.py | 3 | 98.21% | ||
<!-- | Total: | 3 | --> |
Totals | |
---|---|
Change from base Build 9669839231: | 0.04% |
Covered Lines: | 3208 |
Relevant Lines: | 3472 |
Honestly, I basically just forgot that for-loops are not actually macros. Ideally, this behaviour would come from a shared parent class, like
StaticComposite
analogous toStaticNode
. Unfortunately, that gives circular imports because the creator object is onComposite
. OnceWorkflow
andMacro
do not share access to the creator, such an abstraction will be possible. In the meantime, I just tolerate the once-duplicated code.