Compile filters in call node

[ilyapuchka]

Resolves #76

[AliSoftware]

In addition to the linter violation to fix, could be nice to update the tag's doc as we're at it to add an example using one or multiple arguments using filter expression(s) to show in the doc that it's now possible 😉

[AliSoftware]

I generally agree with this code style too when chaining flatMaps but our linter disagrees there, so maybe adapt the syntax here, like let variables = node.arguments.flatMap { ($0 as? FilterExpression)?.variable }?

[AliSoftware]

I think there was another linting violation reported by the CI — but on BoolFiltersTests (which is strange because you didn't change it in that PR, maybe a leftover violation that passed though just at the time migrated to CircleCI 2 and the PR checks had to change to adapt and we missed that and let it slip, idk? would need fixing anyway so might as well fix in this PR)

[ilyapuchka]

@AliSoftware which one? I don't see errors or warnings in the lint logs

[AliSoftware]

@ilyapuchka Nvm, false alarm, my bad.

The story is that I looked at the CircleCI report from my iPhone, but since CircleCI isn't really responsive and doesn't display the logs in a super-adapted way on mobile, I got confused by the console logs. The console writes Linting 'ParseBoolTests.swift' (6/12) just before the first /Users/distiller/project/Tests/StencilSwiftKitTests/CallNodeTests.swift:41:21: warning: Trailing Closure Violation: Trailing closure syntax should be used whenever possible. (trailing_closure) so I first misread that on my tiny phone screen as the violation being the result of linting ParseBoolTests.swift… 🤦‍♂️

[AliSoftware]

Might want to ask @gushromp (OP on #76) to test if that PR/branch fixes their issue, but looking at the changes from here on GitHub, LGTM.

[AliSoftware]

Ah, just missed that remark though:
Missing two spaces at the end of the line after the . — for markdown formatting purposes

(we should def add a Dangerfile and rule for linting our CHANGELOG one day, just never had time to write one for our specific CHANGELOG formatting convention yet)

[AliSoftware]

👍