Skip to content
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

Fixing pickling directory info #106

Conversation

JackMatusiewicz
Copy link
Contributor

This fixes our issue regarding the pickling of a directory info. I've chosen to move the custom pickler up, rather than changing where the isUnsupportedType check happens. The rationale behind this is that if a user provides a custom pickler that is probably what should be used.

Copy link
Member

@eiriktsarpalis eiriktsarpalis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would rather have isUnsupportedType move below the PicklerFactory branch. Primitives and Reflection types are not meant to be overrideable as that would break the library.

@JackMatusiewicz
Copy link
Contributor Author

Fixed, do you think a comment would be useful explaining why the unsupported check is now part way down the list?

@eiriktsarpalis
Copy link
Member

Sure, maybe even a test that demonstrates DirectoryInfo is serializable using a custom pickler would be good.

Adding comment explaining move
Adding a test to show that serialising a directory info works.
Moving test to xml serialiser
@eiriktsarpalis eiriktsarpalis merged commit 0718528 into mbraceproject:master May 14, 2018
@eiriktsarpalis
Copy link
Member

Thanks

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

Successfully merging this pull request may close these issues.

2 participants