[REFACTOR] Update NyxEngine as a singleton that holds instances for main subclasses
#39
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[REFACTOR] Update
NyxEngineas a singleton that holds instances for main subclassesOverview
The
NyxEngineclass has been updated to be a singletime that holds instances for the mainsubclasses. This change was made to simplify the process of accessing the main subclasses and to
ensure that only one instance of each subclass is created.
Now any class that needs to access the main subclasses can do so by calling the
NyxEngineclass,which brings along with it the correct instances of the main subclasses.
This solves:
project grows).
and only "allowing" them to be created in the
NyxEngineclass.NyxEngineclass is responsible formanaging the instances of the main subclasses and providing them to other classes.
Changes Made
Changes were fairly widespread across the project, but the main changes were made were:
NyxEngineclass to be a singleton.NyxEngineclass' instance.access the instances from the
NyxEngineclass.TermUtilsclass to gracefully handle when operating outside of aterminal environment.
Closes #37, #38