-
Notifications
You must be signed in to change notification settings - Fork 87
Replace BinaryFormatter with DataContractSerializer #641
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
Merged
+23
−7
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
f5000e9
Replace BinaryFormatter with DataContractSerializer
MiroBrodlovaUnityGit d19b3f3
Merge branch 'master' into fix/replace-binaryformatter-use
MiroBrodlovaUnityGit ba59411
Use binary XML format for DataContractSerializer
MiroBrodlovaUnityGit 49d9689
Merge branch 'master' into fix/replace-binaryformatter-use
thomas-tu File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
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.
just wondering how does this work in terms of backward compatibility? For older projects tha thave saved using the old BinaryFormatter, would using DataContractSerializer work?
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.
This is an excellent question, thanks for asking it!
Replacing the
BinaryFormatteris indeed a breaking change, or at leastDataContractSerializercannot correctly read data written by theBinaryFormatter. So old projects that have KdTree data saved usingBinaryFormatter.Serialize()will not be able to load those files after this change. There are other packages that are facing the same situation, such as Addressables (you can see some of our discussion here in their PR about it)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.
We've discussed this a bit within the team (I'm in
Scripting Runtime), and have discussed how each team that uses BinaryFormatter will be most well-versed in the needs of their users and package, and so we leave it absolutely to your discretion how you wish to replace it of course. We need to haveBinaryFormatterreplaced in all packages before we'd turn onCoreCLR(as it is not compatible withCoreCLR), so it will be a blocker forCoreCLR(just sharing in case it's helpful to take into account)What are your/your team's thoughts?
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.
I've looked at the code and it seems that we don't really save/load anything with Kdtree. We use it more specifically when the user triggers a weld on the vertices and that's it. So I think it should be safe.
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.
Wonderful Thomas! Thanks for looking into it 🙏
Feel free to at any time merge the PR in that case as soon as it looks good to you/your team! Or of course feel free to change it in any way to suits the need of your package!