Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ScopeLifeCycle flag to distinguish internal and application binds? #100

Open
jbee opened this issue Jul 28, 2020 · 1 comment
Open

ScopeLifeCycle flag to distinguish internal and application binds? #100

jbee opened this issue Jul 28, 2020 · 1 comment

Comments

@jbee
Copy link
Owner

jbee commented Jul 28, 2020

Allow to mark binds as internal.

Internal binds are those used by the container to allow customisation of behaviour but they do not make a part of the application. For example Scope instances are typical internal instances. A simple form could be to consider all instances with scope container as internal. A bit more flexible would be if the ScopeLifeCycle has a internal flag field which can be flipped and which would be true for the container scope by default.

The effect of internal scopes would be that lookup would be categorised as internal or external and for external access these resources would be invisible.

@jbee jbee added this to the 19.1 milestone Jul 28, 2020
@jbee jbee self-assigned this Jul 28, 2020
@jbee jbee added the doubtful label Jul 28, 2020
@jbee
Copy link
Owner Author

jbee commented Jul 29, 2020

A way to apply the limitation to non internal resources is to wrap the Injector. This could be done as last step before the bootstrapped Injector is returned and/or only when injecting the Injector itself.

@jbee jbee removed this from the 19.1 milestone Aug 8, 2020
@jbee jbee changed the title Internal Binds ScopeLifeCycle flag to distinguish internal and application binds? Dec 19, 2020
@jbee jbee removed their assignment Jan 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant