Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Allow indexed non-empty arrays being valid parameter values #106
Currently, there is no way to store indexed arrays as values except direct call
By the way, it's impossible to discern type of parameter (simple value or service) in case of empty array.
P.S. I didn't add this feature for
Thanks for that work, still I'm conflicted: indeed, that's a problem that we can't define arrays for now. But this solution is only partial: it works only for non-indexed and non-empty arrays.
So there's confusion with that solution, because users might think that it's possible to define arrays, whereas it's very restricted.
Anyway that's a fundamental problem, your solution could be merged for a 3.x version. For 4.0, I'd like to fix this definitely (don't know yet what's the best solution for that).
I prefer this one to be honest:
In 3.x it's possible to create method like
Container without arrays is very restricted for me. For instance, I cannot define list of emails for reports. Current format doesn't allow me to call some method twice. So I cannot define dependency neither
That's what I was thinking for 4.0. It's less "simple", but at least it will allow to offer 100% functionalities.
+1, totally right
Yes I'm facing the same limitations, that's why I want to move 4.0 forward.
So to sum up, OK to merge this feature in 3.4 while waiting for a better solution for 4.0.
I'll do it later I can't right now.