Claus Due

Couple of things come to my mind: * I would not object to detecting arrays this way as well because I know the use case all too well. * I'd...

Btw, thinking out loud regarding `_all` we could replace that with `*`: * `` * `{f:render(partial: 'Test', arguments: *)}` ...and make it exclusively a different way of detecting *arrays*. This...

Proof of concept for TagBasedViewHelper conversion to Trait in the form of `RendersTag`: https://github.com/TYPO3/Fluid/pull/230

I would strongly urge to not support quoted strings because aribrary strings within inline syntax has a very high risk of breaking the parsing engine in v2. While we can...

No, what I mean is we shouldn't allow arbitrary strings at all - quoted or otherwise. Basically, treat everything as a variable. The problem is that the parser (v2, being...

Hi @dax-jones - welcome to GitHub, looks like you created an account just to report this issue so that's appreciated! About your points: * The formatting is being taken care...

While I understand the problem, there are some challenges and disconnects that mean this isn't a simple matter: * NumericNode is a parse-time construct and it only gets used for...

> @NamelessCoder Why does the parser need to decide a node-type? It could take all arguments as strings. (Actually it's not even the job of a parser.) I don't know,...

@Jabychan please review my earlier notes in this thread, there are several workarounds at this time and they now include `f:variable` through which you can assign a variable directly in...

Closed as duplicate - and is fixed in `development`.