generated from snivilised/astrolib
-
Notifications
You must be signed in to change notification settings - Fork 0
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
formalise bootstrap phases #29
Labels
feature
New feature or request
Comments
Just been watcing a video (Solid programming - No Thanks) by the Primeagen discussing SOLID and he mentioned (during the discussion about Dependency Inversion Principe) a convention in Go where when writing methods/functions, you should receive interfaces but return structs. Something to think about. |
plastikfan
added a commit
that referenced
this issue
May 20, 2024
plastikfan
added a commit
that referenced
this issue
May 20, 2024
plastikfan
added a commit
that referenced
this issue
May 20, 2024
plastikfan
added a commit
that referenced
this issue
May 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
this is a continuation of issue #22
Identified phases are:
So the navigator can be created and intialised independent of features. The navigator can will expose an interface for use by features. Some navigator properties should not be readily available, eg the ability to intercept filters as requred by hibernation should only be avilable to hibernation feature, therefore the navigator can expose another interface with an intercept method that can be queried for.
Feature can if they require hook into life cycle events.
The text was updated successfully, but these errors were encountered: