Refactored save integration to allow for arbitrary save data container objects (#317) #318
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
#317 Implemented generic save data container support for flow.
The Flow Subsystem now saves and loads from any
UObjectimplementing the newIFlowSaveDataContainerInterface. The interfaces provides mutable and const access to the newFFlowSaveDatastruct, which wrapsFFlowComponentSaveDataandFFlowAssetSaveData.To retain compatibility with
UFlowSaveGame, that class now implements the new interface, thus projects can easily switch to the new API on the subsystem. I've marked the old API as deprecated.