-
Joined on
2021-11-20
norb
deleted branch 2026-03-30 15:09:24 +00:00
53687/task-support-instance-specific-cfg-write-target-v2 from rabe/Util-Settings
Task: #53687 Support instance-specific cfg write targets and add coverage V2
norb
pushed to 53687/task-support-instance-specific-cfg-write-target-v2 at rabe/Util-Settings
2026-03-30 15:04:40 +00:00
norb
pushed to 53687/task-support-instance-specific-cfg-write-target-v2 at rabe/Util-Settings
2026-03-30 14:58:05 +00:00
Task: #53687 Support instance-specific cfg write targets and add coverage V2
probably most of this should be done in the validator as well
Task: #53687 Support instance-specific cfg write targets and add coverage V2
can you do this as validators? e.g. c6fe64321e/example/example.php (L35)
Task: #53687 Support instance-specific cfg write targets and add coverage V2
perhaps we could have a verbose mode?
Task: #53687 Support instance-specific cfg write targets and add coverage V2
I don't really like this .. seems over complicating the code. It is just for beging able to have different order of arguments?
Task: #53687 Support instance-specific cfg write targets and add coverage V2
as agreed in chat, again to keep the code simple, use --siteDir without alias
Task: #53687 Support instance-specific cfg write targets and add coverage V2
our coding style would always put the opening curly bracket on a newline. I retain it specially important if the following codeblock is longer than a couple of lines