[DI] Deprecate non-string default envs #27808
This is a failing test to further clarify the issues raised in #27680
So given #27680 (comment)
I think it solves a real bug :)
Isnt that over-complicated? IMHO there's only one real env, and thus only 1 default for it as well.
Following your logic we could do:
Im not sure that makes sense... or at least is extremely hard to reason about.
Which we do already, the processors defined on the reference-side (e.g. for
Status: Needs Work
Status: Needs Review
Jul 3, 2018
You can't ... :)
Ok, let's use
I.e. the prefixed default is not used, which is the same behavior during config validation:
No. It will only trigger a deprecation declaring default env as non-string.
And given any prefixed default env is not used today, i think we should deprecate that as well :) and open-up whenever it's actually supported (of which i'm not sure we should do it).
Correct, it's still a failing test only :) to move forward the open questions are