Feature #26665
Fluid: Implement String comparison
Status: | Resolved | Start date: | 2010-03-10 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | - | % Done: | 100% |
|
Category: | - | |||
Target version: | - | |||
Has patch: | No |
Subtasks
Related issues
History
#1 Updated by Sebastian Kurfuerst about 4 years ago
- Subject changed from Fluid: Improve ViewHelpers to Fluid: Implement String comparison
- Position deleted (
1) - Position set to 1
#2 Updated by Bastian Waidelich about 4 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)
#3 Updated by Bastian Waidelich about 4 years ago
Note: I added an entry to the Extbase FAQ: http://forge.typo3.org/projects/typo3v4-mvc/wiki/FAQ#Can-I-compare-strings-with-the-if-view-helper
#4 Updated by Sebastian Kurfuerst almost 5 years ago
- Tracker changed from Story to Feature
- Target version changed from 1.0 beta 1 to 1.0 beta 2
#5 Updated by Sebastian Kurfuerst almost 5 years ago
- Project changed from TYPO3 Flow Base Distribution to TYPO3.Fluid
- Priority changed from Must have to Should have
#6 Updated by Robert Lemke almost 4 years ago
- Target version changed from 1.0 beta 2 to 1.0.0
#7 Updated by Robert Lemke almost 4 years ago
- Target version changed from 1.0.0 to 1.1
- Has patch set to No
#8 Updated by Karsten Dambekalns about 3 years ago
- Target version deleted (
1.1)
#9 Updated by Alexander Berl over 2 years ago
Is there anything left to do or can this issue get closed?
#10 Updated by Stefan Neufeind over 2 years ago
Was fixed with 6757. Imho done.
#11 Updated by Adrian Föder about 2 years ago
- Status changed from New to Resolved
Definitely resolved.