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
It would be helpful if we could expose the control of how methods operated with parameters such as:
merge - Informs if the method's output is merged into the top level keys - the default behaviour. False would keep the data under the method name (see below).
try / except - Wrap method with try accept
for - Run the method on some loop
?
Example - merge:
MyHook<-:
foo: barmy_method:
<-:
bar: bazmerge: Falseexpected_output:
foo: barmy_method:
bar: bazassert->: | {{MyHook.my_method()}} {{expected_output}}
This should not be super hard to implement as methods are just hooks which can have hook_call parameters which can be injected in. Only issue is the merge functionality needs to be modified or rethought since right now it is the default. So in the future that will need to be parameterized.
The text was updated successfully, but these errors were encountered:
Method Properties
Methods could have properties which inform their behaviour
Proposal Status: wip
Issue Number: 242
Proposal Doc: method-properties.md
Overview
It would be helpful if we could expose the control of how methods operated with parameters such as:
merge
- Informs if the method's output is merged into the top level keys - the default behaviour. False would keep the data under the method name (see below).try
/except
- Wrap method with try acceptfor
- Run the method on some loop?
Example - merge:
This should not be super hard to implement as methods are just hooks which can have hook_call parameters which can be injected in. Only issue is the merge functionality needs to be modified or rethought since right now it is the default. So in the future that will need to be parameterized.
The text was updated successfully, but these errors were encountered: