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

[RESEARCH] Consider slowly shifting various singleton managers to their own instances #19

Open
5 of 9 tasks
japtar10101 opened this issue Sep 11, 2019 · 1 comment
Open
5 of 9 tasks
Assignees
Labels
needs-priority Indicates the priority of the issue has not been determined yet. This is the default priority. question Further information is requested split to a package A de-coupling task to split a feature in this project into its own Unity package repository.

Comments

@japtar10101
Copy link
Member

japtar10101 commented Sep 11, 2019

Describe what to research into

Evaluate and create issues based on the effort it would take to shift the following singletons to their own script:

Additional context

Carry-over from the old Bitbucket Mercurial project:
https://bitbucket.org/OmiyaGames/hg-template-unity-project/issues/66

@japtar10101 japtar10101 added question Further information is requested needs-priority Indicates the priority of the issue has not been determined yet. This is the default priority. labels Sep 11, 2019
@japtar10101 japtar10101 added the split to a package A de-coupling task to split a feature in this project into its own Unity package repository. label Dec 29, 2019
@japtar10101
Copy link
Member Author

For some of these Singletons, converting them into a SettingsProvider might be the best choice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-priority Indicates the priority of the issue has not been determined yet. This is the default priority. question Further information is requested split to a package A de-coupling task to split a feature in this project into its own Unity package repository.
Development

No branches or pull requests

1 participant