Feature #26665

Fluid: Implement String comparison

Added by Sebastian Kurfuerst about 2 years ago. Updated about 1 month ago.

Status:Resolved Start date:2010-03-10
Priority:Should have Due date:
Assignee:- % Done:

100%

Category:-
Target version:-
Has patch:No
Votes: 8 (View)

Subtasks

Task #6757: support literal strings in boolean argumentsResolved


Related issues

related to TYPO3.Fluid - Feature #33394: Logical expression parser for BooleanNode Needs Feedback 2012-01-23
duplicated by TYPO3.Fluid - Bug #29004: if viewhelper does not evaluate conditions correctly Closed 2011-08-16
duplicated by TYPO3.Fluid - Feature #26692: String comparison support for f:if Rejected 2011-05-07

History

Updated by Sebastian Kurfuerst about 2 years ago

  • Subject changed from Fluid: Improve ViewHelpers to Fluid: Implement String comparison
  • Position deleted (1)
  • Position set to 1

Updated by Bastian Waidelich about 2 years ago

Some behaviors that I would expect from this feature:
given:

$this->view->assign('someString', 'foo');

satisfied conditions (true)

1 <f:if condition="{someString} == foo">
2 <f:if condition="foo == {someString}">
3 <f:if condition="{someString}  ==  foo">
4 <f:if condition="{someString} != bar"> (other comparators should behave like their PHP dependant)
5 {f:if (condition: '{someString} == foo')}

unsatisfied conditions (false)

1 <f:if condition="{someString} == bar">
2 <f:if condition="bar == {someString}">
3 <f:if condition="someString == foo"> (or should this throw an exception?)

parser exception

1 <f:if condition="{someString} == foo bar"> (not sure, whether strings containing spaces should be supported)
2 <f:if condition="{someString} == foo != bar"> (more than one comparator)
3 {f:if (condition: someString == foo)} (not sure, if it is easily possible to detect this case)

Updated by Sebastian Kurfuerst almost 2 years ago

  • Tracker changed from Story to Feature
  • Target version changed from 1.0 beta 1 to 1.0 beta 2

Updated by Sebastian Kurfuerst almost 2 years ago

  • Project changed from TYPO3 Flow Base Distribution to TYPO3.Fluid
  • Priority changed from Must have to Should have

Updated by Robert Lemke almost 2 years ago

  • Target version changed from 1.0 beta 2 to 1.0.0

Updated by Robert Lemke over 1 year ago

  • Target version changed from 1.0.0 to 1.1
  • Has patch set to No

Updated by Karsten Dambekalns about 1 year ago

  • Target version deleted (1.1)

Updated by Alexander Berl 3 months ago

Is there anything left to do or can this issue get closed?

Updated by Stefan Neufeind 3 months ago

Was fixed with 6757. Imho done.

Updated by Adrian Föder about 1 month ago

  • Status changed from New to Resolved

Definitely resolved.

Also available in: Atom PDF