Claus Due

I'll check the recursion issue but I should note that the expression is definitely not going to be supported. I assume these are placeholder values, but: * Ternary conditions do...

Without testing, I expect Fluid 3.0 to either report a parsing error or parse much more content than expected, as part of the single-quoted string. Main problem here is that...

I kind of have a PoC for that (f:sections to import sections from named partial, you can then render and/or override them locally) but because it's the "wrong way" in...

Please do not use this (officially unsupported) syntax. Hardcoded string values are "working" only by coincidence and should not be allowed by design - but the use of an incorrect...

Without going into too much detail that isn't relevant here: the problem is that the content of your expression has to be detected with regular expressions. Those expression detections currently...

Exactly - this is a scheduled change. We will address this soon!

https://github.com/NamelessCoder/TYPO3.Fluid.Lint/blob/master/src/FluidTemplateLinter.php#L107 might be a place to add syntaxtree-level checks, assuming the necessary node structure can be read (may require making internal Fluid API semi-public).

Thanks for the detailed report! I found this suspect: https://github.com/TYPO3/Fluid/blob/master/src/Core/Parser/SyntaxTree/BooleanNode.php#L109 The call to `is_string` does not also check if the string is empty and I think that's where all the...

This would actually have been rebased away since it got fixed in another PR ;)

Not sure it's wasted, I went the way of more or less writing out the entire fluid expression for easier debugging: https://github.com/TYPO3/Fluid/pull/396/files#diff-273f993b0da6a2bc91976237ec4881b6R45 - not sure which one to prefer. The...