bruno messias

@hauntsaninja I don't get. The vendoring solution for this issue must be done in the refurb pacakge right?

@JelleZijlstra I just made a search here, why this will not create the same issue in InspectionStubGenerator? 

Well, wouldn't it also be possible to have an ugly solution with duplicated code TraverserVisitor (with trait) and TraverserVisitorExt

I found that var('foo', 10 ) * 1} dosen't work but var('foo', 10 ) works because the template is rendered with no var object specified. So var("foo", 10) will not...

I like this. Especially because the unit tests are now broken when we have ctx like vars inside the model. The way I was handling this was by commenting them...

Hi @CraigWilson-ZOE, I understand that you are sharing the compiled SQL rather than the model, correct? Could you please share it with me? I’d like to see if it’s similar...

Why I'm saying that @CraigWilson-ZOE . Your compiled sql is wrong due the double "..", which will be the result of unit test if you have a model like this...

I think it's a good idea if you post the model.sql file you're having issues , @kangshung

Hi @kangshung, I see! So, this seems to be a different issue from the one originally reported here, right? From my testing, it doesn’t appear to be related to the...

This is a minimal example to obtain the same issue pointed by @kangshung ```yaml #_unit_tests.yaml version: 2 unit_tests: - name: test_2 model: my_model given: - input: source('source_name', 'my_model') rows: -...