A modern programming language that makes developers happier.

kotlinlang

After talking to <@U25U0KPFT> and thinking about the tenant scope some more I think I'll try a solution that will work for the JPro case and also give some manual control over scoping, but it will not be an enterprise feature like scoping is in Java EE for example. Basically you configure a scope for any originating app, view or fragment. Then all injected components will share the same scope unless you specify a different scope to `inject()` or `find()`. This will be unobtrusive and have a very small footprint and probably easy to understand and reason with. I think we should flag this feature as a beta feature for a while with a warning that the API might change. API-wise it will consist of a variable in component and the parameter to `inject()` and `find()`. That's basically it. I tried this approach early on but with another mindset so I was never satisfied with it. By accepting that it will not be everything for everyone, and maybe even just a special feature to support JPro and possibly similar frameworks in the future I came to the conclusion that it is "good enough" at least for now. I really need to get back to documentation and screencasts and also the kitchen sink app, so I will try to implement this tomorrow in a feature branch and see how it feels.