Olivier Halligon

I'd personally lean to a syntax like `viewA.layout.left = 0.3 * viewB.layout.height + 10`, feels more natural. The `constrain` scope is nice, but would need to pass the views ahead...

While waiting for this inheritance feature to be available, is there any workaround, like a good practice to design our RLMObjects and model to make such use cases possible? My...

Mmmh good question. Is it: - The job of the `replace` filter itself - The job of Stencil itself (which would allow to fix that issue for all tags, but...

Yeah the parsing itself shouldn't be changed, but should we or should we not convert newlines to `\n` when we build the context from those parsed content, or is that...

Yeah which is why I'm starting to wonder if it shouldn't be Stencil's job to do that un-escape, instead of each filter individually…

PS: just missing an `{% endfilter %}` in the macro and for blocks of your example @djbe 😉

@djbe You can't hide 😄

One idea I pitched in our Slack was to create a new filter named `call` in StencilSwiftKit, that would take as a parameter the name of a 1-arity macro defined...

I actually didn't take the time to investigate which mock files were involved and if we already passed the locale as parameter, so this is great and useful info @pachlava...

Note that once https://github.com/wordpress-mobile/WordPress-Android/pull/17096 lands, updating the API level of the emulators used to take screenshots should mostly be a matter of updating the `SCREENSHOT_DEVICES` constant in `fastlane/lanes/screenshots.rb` [here](https://github.com/wordpress-mobile/WordPress-Android/pull/17096/files#diff-7f448e8d33ef3a5a6c249acf5737243310e667d8673cd96a2b1405ce3b3a1384R8-R19)