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.

Sign up for GitHub

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

Jump to bottom

Configuration for default component scope #991

Open
GuusLieben opened this issue Oct 10, 2023 · 0 comments
Open

Configuration for default component scope #991

GuusLieben opened this issue Oct 10, 2023 · 0 comments
Labels
contribution: good first issue discussion Open for discussion in: core type: feature request
Milestone
0.7.0

Comments

@GuusLieben
Copy link
Member

Related problem

Currently components are treated as prototypes by default, and services are treated as eager singletons. This behavior was chosen based on their intended purpose, however it is unrealistic to expect this to apply to all scenarios.

Requested feature

Allow changing the default scope for components within a single application context. Note that this is currently indicated by attributes in the component container and related annotations.
@GuusLieben GuusLieben added this to the Release 0.5.1 milestone Oct 10, 2023
@GuusLieben GuusLieben modified the milestones: Release 0.5.1, Release 0.6.0 Nov 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
contribution: good first issue discussion Open for discussion in: core type: feature request
Milestone
0.7.0
Development

No branches or pull requests
1 participant
@GuusLieben