Closed ReservedDeveloper closed 8 years ago
@theofidry I'm currently working on this, fyi
@reinfi did you find a fix for it?
Looking again at this, I think this is just a parsing issue in 2.x. It's quite this kind of bug that are hard to spot and fix in 2.x due to the inexistence of a proper parser/lexer to handle this task. This should however definitely work on 3.x.
If you have found a fix in 2.x I would gladly accept it, otherwise it will be kept as fixed in 3.x only.
Not sure if this is a feature request, bug, or other. Been trying to use the optional setter w/ a self-reference boolean field.
Rough idea:
Seeing that optional data seems to prefer ###? <provider()> syntax, I also tried
<($someBool ? 100 : 0>%?
. Wondering if the optional return might be kicking back a string instead of a null value, I also triedconditionalArray: @self->someBool? <myArrayProvider()> : <myEmptyArrayProvider()>
In each instance I received the following error:
I suspect one of the following is at play: a) This has been addressed, but the fix version is not being referenced by AliceBundle yet. b) Expressions cannot be used for the optional portion of a fixture. c) Identity cannot be combined with the optional portion of a fixture. d) Custom providers cannot be combined with the optional portion of a fixture. e) ???
For the time being, I've split my fixtures out in to true & false varieties. However, I'd appreciate any insight on the above!