Jonas Eberle
Jonas Eberle
That's a good idea to reduce duplication. I still don't think it's easy to read but that's for sure the best way right now. I'll update my initial post.
Renamed the attribute from `f:wrapIf` to `f:renderTagIf`, too. `f:if` might imply that the content is not rendered, `f:tagIf` might be too compact.
Thank you for the code snippet. If you have the content as variable, that might help. I do not agree with your judgement, though. 1) Fluid should not only focus...
Ok, lets make pull requests to fluid_styled_content and see where we go from there. So to at least have good examples in any default TYPO3 installation ;) I'll see how...
@ochorocho I don't think your workaround is too bad if you want to have it in different CI stages. We also build with Surf: ``` ->defineTask( 'BuildTask', LocalShellTask::class, // could...
> What if the target is/should be a file? Then you should create it beforehand. It won't act if anything (file/dir/link) is already there at that path.
My use case is the default case for the initial deployment of a TYPO3. At that point, directories in `shared/Data` need to be created. I miss the use case where...
How should we continue here?
That test in deployer does not make a lot of sense since it tests for directory only. That check is included in `mkdir -p` already (https://www.gnu.org/software/coreutils/manual/html_node/mkdir-invocation.html). Let's check for anything...
I just rebased on top of current master. I don't see any risk of regression. The check if the target exists as suggested by @sabbelasichon have been added.