Extend FsPickler static methods to accept IPicklerResolver parameter. #126
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
Extend FsPickler static methods to accept IPicklerResolver parameter.
Add missing overload and update docs
Author
|
@eiriktsarpalis could you take a look on this PR? 😄 |
Author
|
@eiriktsarpalis could you take a look on latest changes? Thanks! |
Member
|
I'm pretty swamped with regular work at the moment, I'll take a look at some later point. Sorry! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR tries to resolve issue I found as part of extending Vagabond to use custom
IPicklerResolver. I've noticed it works fine with Serialization butVagabond.ComputeObjectDependenciesuseFsPickler.VisitObjectthat's currently missing support for providing custom resolver.This change is not binary compatible as it's add optional parameter but I'm happy to update it as new methods overloads if needed.
It's partially related to #123