Releases: brunomikoski/ScriptableObjectCollection
Releases · brunomikoski/ScriptableObjectCollection
Fix possible AOT issues
Changed
- Changed the
ResourceScriptableObjectSingleton
to have generic type on methods again, to prevent AOT issues.
Delete Collection and bug fix
Added
- Added Delete Collection button under advanced settings, I will delete all the related assets and unregister from the registry
Changed
- Renamed the
Settings
menu on the Collection Editor toAdvanced
- Fixed an issue when drawing indirect references inside arrays.
Keyboard Shortcuts
Added
- Added arrow navigation on the Collection Editor, now you can navigate between items and expand/collapse it by left right
- You can now expand/collapse all items by holding alt while clicking on the foldout arrow, like default unity controls
Using ReorderableList on the Collection Editor.
Changed
- Refactored the
ScriptableObjectCollection
Custom Editor
to useReorderableList
instead of the previous custom list drawer - Refactored the editor prefab property drawer to properly draw the
SerializedProperties
of the item instead of displaying the custom inspector - Removed some old files and methods that aren't necessary anymore.
- When using the inline visualizer of the CollectionItem, it should now respect position (if is inside an array or custom propery drawer)
Added
- Added context click on the items, you can now Copy Paste values between collection items and Duplicate and Delete items when right click on it on the Editor
Hotfix - Destroying Collection
Changed
- Removed the asset destruction of the Collection on the
OnDestroy
event
IndirectReference Refactor
Changed
- Improved the Refreshing of the
CollectionRegistry
to try to refresh when items are deleted/created - Refactored the
IndirectReference
to not need a serialized version of theCollectionItem
type, so avoid any serialization issues - Renamed some of the editor classes to match the standard
Multiple Collections improvements
Changed
- In order to support multiple collections of the same type the check of the
Values
I had to tweak how the instance of every instance is assigned, changed for theOnEnable
of the collection item - Changed the Refresh of the collections to only find items under the same folder.
- Fixed a lot of scripts to work properly with multiple collections of the same type
- Added some logs when
CollectionItems
are added/removed from collections to help the visibility CollectionType.Values
now will return all theCollectionItem
available on the registry, so if you have 2 Collections of the one Type this will return the content of both collections while theCollectionItem.Values
when the access file is generated will only return that specific collection item
Settings Revamp
Changed
- Removed the automatically reload of CollectionRegistry using the
DidReloadScripts
callback, this caused multiple issues on batch mode and on clear libraries - Converted the
Collection
reference on theCollectionItem
to be a Lazy reference, since this was causing some dependency when usingCollectionItem
as addressables - Refactored the
ScriptableObjectSettings
this used to be a Resources object that was autoloaded, but this could also create unwanted dependencies between items. The settings for code generated are not stored inside the Collection itself. Make sure you delete theScriptableObjectsSettings
ScriptableObject inside your resources folder. - Added a bunch of validation and verification for the Generation of the static access, making sure it only allows partial classes when is possible and other small checks.
- The settings are now on the Project Preferences where you can define the default folder for the Scriptable Objects and default namespace.
Fixed batch mode collection reload
Changed
-Disabled the reload of the collection after script reloading on batch mode.
Cleanup old .meta files
v1.5.2 Update package.json