Skip to content

Remove allowMultipleInstances #30

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

Merged
merged 2 commits into from
Nov 12, 2019

Conversation

anaisbetts
Copy link
Contributor

When the user calls asNewInstance, they are already indicating that they know what they're doing - we don't need to add an extra safety to this

When the user calls `asNewInstance`, they are already indicating that they know what they're doing - we don't need to add an extra safety to this
@escamoteur escamoteur merged commit 4eaafb1 into fluttercommunity:master Nov 12, 2019
@escamoteur
Copy link
Collaborator

Yeah I agree that was before we had the asNewInstance when GitIt wasn't a Singleton

@escamoteur
Copy link
Collaborator

Publishing this would be a breaking change. How should we deal with that?

@anaisbetts
Copy link
Contributor Author

@escamoteur While it's technically a breaking change, it's really easy to handle - just delete all the AllowMultipleInstances lines. It won't actually give anyone stress

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants