-
Notifications
You must be signed in to change notification settings - Fork 51
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
Fixing pickling directory info #106
Conversation
Fixing formatting
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.
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.
Fixed, do you think a comment would be useful explaining why the unsupported check is now part way down the list? |
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
Thanks |
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.