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
Class dependencies allow setting (temporary?) ctx variables for an operation.
Currently, those variables stay in the result ctx and hence bleed through to the outer operation when nested. Maybe an expose: true could configure this?
Currently, in #public_call and #call_with_circuit_interface we create a new Context where those variables are set.
Ideally, we should use :inject and/or :input instead in the outer operation and set the inner class variables with an injection. This would also reduce run-time logic. E.g. the Subprocess() macro could take care of this.
For the topmost operation, the endpoint could be doing this, instead of clumsily hacking this feature.
The text was updated successfully, but these errors were encountered:
Class Dependencies
expose: true
could configure this?Implementation
#public_call
and#call_with_circuit_interface
we create a newContext
where those variables are set.:inject
and/or:input
instead in the outer operation and set the inner class variables with an injection. This would also reduce run-time logic. E.g. theSubprocess()
macro could take care of this.The text was updated successfully, but these errors were encountered: