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

Do not expose DefaultLifecycle from IContainer. #716 #717

Merged
merged 1 commit into from
Apr 17, 2017

Conversation

bnordli
Copy link
Contributor

@bnordli bnordli commented Jan 7, 2017

Instead clients should set the default lifecycle on the container either
before returning from ICanCreateContainer.CreateContainer or before the call to Configure.With.

Original issue: ProCoSys#16

Original commit: ProCoSys@7393a03

Instead clients should set the default lifecycle on the container either
before returning from ICanCreateContainer.CreateContainer or before the call to Configure.With.

Original issue: ProCoSys#16
@einari einari modified the milestone: 1.2.0 Jan 13, 2017
@einari
Copy link
Contributor

einari commented Jan 13, 2017

I'll have to look into it and consider the effect of this as it is a breaking change. For now I've marked it as a minor change - although it is an API change and should be part of a major release, this is probably not as severe

@bnordli
Copy link
Contributor Author

bnordli commented Jan 16, 2017

Sounds reasonable. (The methods will be rewritten again if you want to take my yet-to-come Configuration pull request, I just think this is a valuable addition as is.)

@einari einari modified the milestones: 1.2.0, 1.3.0 Apr 13, 2017
@einari einari added the ready label Apr 13, 2017
@einari einari self-assigned this Apr 13, 2017
@einari einari merged commit ceda934 into dolittle:master Apr 17, 2017
@einari einari removed the ready label Apr 17, 2017
@bnordli bnordli deleted the issue/716 branch April 17, 2017 07:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants