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

Private bindings #1968

Open
pshirshov opened this issue Jun 23, 2023 · 2 comments
Open

Private bindings #1968

pshirshov opened this issue Jun 23, 2023 · 2 comments

Comments

@pshirshov
Copy link
Member

pshirshov commented Jun 23, 2023

We might want to support "private" bindings which would never be exposed in Locators produced by the interpreter.

It might be useful to, for example, hide bootstrap context members from the rest of the application.

Alternatively we might hide everything apart from the graph roots and an optional list of "public" keys.

We should add a way to tell produce to respect private declarations and this should be on by default. There still may be situation when user might want to make everything public.

@neko-kai
Copy link
Member

We might want to declare 'privateness' on memoization level itself, not on the module. So e.g. we want docker memoization level to not pass on Clock instance further, but we don't want Clock to be non-singleton on every single level of memoization.

@lukoyanov
Copy link

Sounds like a great feature 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
DIStage
  
To do
Development

No branches or pull requests

3 participants