-
Notifications
You must be signed in to change notification settings - Fork 851
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Refactor SlotMap and Slot classes #896
Conversation
Ensure that Slot and all related classes are separate classes now and not just nested inside ScriptableObject. Also, break the two Slot implementations (regular and "GetterSlot") into four so we can use inheritance rather than complex "instanceof" logic to implement the different types of slots. This will be helpful as I'd like to introduce a lambda-based Slot and it was too much complexity the old way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like a real improvement, did not found the time to dive into the details - but one suggestion:
What about placing all the different slot implementations in an separate sub package?
I'm going to experiment with a different package -- but it's going to make this an even bigger PR. |
Moving the package is going to result in a ton of changes because of use of package-protected fields and methods. I'm going to leave these classes in the main package and we might consider a change at a future time. |
Ensure that Slot and all related classes are separate classes now and not just nested inside ScriptableObject.
Also, break the two Slot implementations (regular and "GetterSlot") into four so we can use inheritance rather than complex "instanceof" logic to implement the different types of slots.
This simplifies the structure and logic and will make it easier to extend stuff later.