Skip to content

KeyValueDefinitionBase non generic as new base class #24

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

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

Hugosslade
Copy link

Created new base class for KeyValueDefinitionBase in the form of KeyValueDefinitionBase. This lets all variable references be serialized in the Inspector without having to serialized ScriptableObject.

Then all KeyValueDefinitions can be found in the project easily.

Created new base class for KeyValueDefinitionBase<T> in the form of KeyValueDefinitionBase. This lets all variable references be serialized in the Inspector without having to serialized ScriptableObject.

Then all KeyValueDefinitions can be found in the project easily.
@ashblue
Copy link
Owner

ashblue commented Aug 31, 2022

Hey this is super clever. I'll run it locally to regression test tonight.

@ashblue
Copy link
Owner

ashblue commented Aug 31, 2022

Hey can you explain the edge case this solves? It just seems like this adds an extra layer of complexity to the KeyValueDefinitionBase<T> but I'm probably missing something. I did some checks and it seems to compile just fine as is right now on MonoBehaviors and ScriptableObject(s) without this fix.

@Hugosslade
Copy link
Author

Hugosslade commented Aug 31, 2022 via email

@ashblue
Copy link
Owner

ashblue commented Aug 31, 2022

That makes sense. I'll QA the search functionality of the type search to verify things tonight after work. Thanks for doing this.

@ashblue ashblue added the enhancement New feature or request label Oct 22, 2022
@ashblue
Copy link
Owner

ashblue commented Oct 22, 2022

Might take a bit of effort to get this adjustment in but I totally see the value of it. Will eventually get in (sorry for the wait). All depends on when I have to swing in again to upgrade the database library.

@ashblue
Copy link
Owner

ashblue commented May 18, 2023

Sorry, still haven't gotten around to updating this branch. It needs some migration work to my latest package generator version.

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

Successfully merging this pull request may close these issues.

2 participants