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

whitelist and blacklist rules on deserialize #16

Closed
hilaryosborne opened this issue Jan 27, 2017 · 1 comment
Closed

whitelist and blacklist rules on deserialize #16

hilaryosborne opened this issue Jan 27, 2017 · 1 comment

Comments

@hilaryosborne
Copy link

Wondering if there are plans (or it is already implemented but im doing it wrong) for blacklist and whitelist rules to apply to deserialize. Currently it seems to be outputting a deserialized version of the data regardless of these rules. I am having to deserialize, serialize and then deserialize to get the clean data.

@danivek
Copy link
Owner

danivek commented Jan 27, 2017

@hilaryosborne Your are right, currently blacklist or whitelist options are only effective on serialization.
I think we can't apply these same options on deserialization. because attributes to remove or keep when serialize or deserialize can be different.

We need a blacklist and a whitelist options on deserialization too. I suggest to add these 2 options :

  • blacklistOnDeserialize
  • whitelistOnDeserialize

Maybe you have a better idea for naming these options ?

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

No branches or pull requests

2 participants