robcxyz

When calling a method within a tackle file, it should be: ```yaml this->: a_hook a_method an_arg not this->: a_hook.a_method an_arg ``` Should still have dot notation for jinja renders. ```yaml...

this should work: ```yaml base

Common situation, I want to keep all my tackle functions in a parent directory and then be able to call them anywhere within the repo. Issue is I would also...

Only when run in python, if there is a tackle.yaml file in the same dir then it get very confuse. ```python os.chdir(os.path.join('func-provider-hook', 'a-dir')) o = tackle('funcs.yaml', 'here', find_in_parent=True) ``` ```...

```yaml : "{{calling_directory}}" calling_file->: "{{calling_file}}" ``` Both these vars are brought into creating a declarative hook and so there is a duplicate value error. ```python Function = create_model( func_name, __base__=BaseFunction,...

``` gen

```yaml gen: - go - python ``` ``` tackle.exceptions.MalformedFunctionFieldException: Error creating hook='gen' in file='tackle.yaml', The field all_languages_> can not be a private hook call (ie ending in '_>') as there...

Handle variables with dashes

1

Dashes don't work in variables names when using them as render vars or as hook names / methods. This is a well known issue with jinja as python doesn't allow...

This breaks inside `nested_set`: ``` do: ->: literal --merge for: - stuff - things input: foo: "{{item}}" ``` Would expect: ``` foo: things ``` Not very useful but when combined...

Would be good to support splat syntax. ```yaml class: "{{class(*inputs)}}" 2->: class *inputs ``` 1 is supported already. 2 is not.