Currently, if a feature declares a provision that's not declared in a configuration mount that feature, the provision becomes local. If multiple features do this, we get to different provisions for each of these features. I called this effect "local provision".
I never made local provisions, they just happened. They're a side effect of how the code is generated. I first thought this was a good idea, a feature, but the more I think about the implications and semantics of local provisions, the more I think they shouldn't exist.
Therefore:
implement all mounted provisions in the configuration, which effectively removes local provisions
implement #99 to allow selecting one provision in case of a conflict
at some later point in the future, we may consider going back to explicit local provisions (#5), but I don't think so, tbh
Currently, if a feature declares a provision that's not declared in a configuration mount that feature, the provision becomes local. If multiple features do this, we get to different provisions for each of these features. I called this effect "local provision".
I never made local provisions, they just happened. They're a side effect of how the code is generated. I first thought this was a good idea, a feature, but the more I think about the implications and semantics of local provisions, the more I think they shouldn't exist.
Therefore: